Gregory Haerr

Got it. Very interesting indeed! I like your solution, definitely just keeping a 64-bit pointer in a long is far easier than adding a pointer with every instruction. In looking...

On another point, when you run the C compiler under the user emulator, (and I'm pretty sure with the protected mode emulator), and choose to run the compiled program output...

One last point - the user mode emulator port required the argv[] array to be rebuilt and pushed onto the stack as 32-bit values, to implement the cool recursive execution...

With regards to your hacked sbrk implementation, check out mine, it correctly emulates sbrk, which requires that the all linear addresses in between sbrk calls are in fact contiguous. Except...

No, both c.c and eu.c get their initial argc/argv from main() and the increment argv for their own options and then pass them to either the compiled code in c.c's...

Ok, I understand you now. Yes, no need to rebox argv for c.c when running in the OS or through the user mode emulator. However, you WILL need to rebox...

I see. So that would eliminate the (uint *) casts that are thrown around and thus compile 64-bit clean? I have studied the compiler but its pretty complicated. Is the...

I have several ideas on the instruction set, and like the idea of a byte code stack machine, rather than a three register machine. I think it simplifies things immensely,...

Another item I've been thinking way too much about is: why does the system ALWAYS use 8-byte pushes for calling functions, and waste such memory when they're only needed for...

Ok so I've tested your new em.c, the good news is works on OSX, I bootstrapped the system using my user mode emulator and a pre-compiled bin/c to compile the...