(12-28-2013, 10:28 PM)mort96 Wrote: I wrote a specification for an IS which I think is pretty neat: http://mortie.org/?webapp=compiler_16/morcore_spec.txt. It should be fairly easy to implement.
Even though your instruction set lacks some necessary features like basic pointer operations and (hardware) interrupt handling, I nevertheless think it's a good IS to base the standard(s) one(s) on. (+1 for the stack)
(12-28-2013, 11:18 PM)WrytXander Wrote: I really love the IS, but one thins that bugged me, was the fact that there were stacks. Not everyone uses stacksor know how to use/implement one.
Really, a stack is necessary as it is the most sane (and probably most efficient) way of implementing (nested) function calls.
(12-28-2013, 11:44 PM)mort96 Wrote: I really don't think multiple variations of the standard IS would be a good idea.
I am actually hoping we can compile a list of "standard" instruction sets (based on the actual target hardware). So, for instance, we can have three categories:
- Basic Processing Units (In essence, ALU + RAM + I/O)
- Advanced Systems (Pointers, Interrupts, Several I/O devices - protocol implementations)
- Multi-core/Multi-user/Multi-thread Systems (Process and User management, Virtual Memory - MMUs e.t.c.)