Some progress to report on Parasol. Ive been working on three areas: 1. Fixing bugs. The C++ Parasol compiler now passes all unit tests. The Parasol self-hosted compiler passes all but one. That one failure is in the var (think of JavaScript var) where issues with runtime type objects break some operations. Fixing this will depend on getting the self-hosted compiler fully operational. 2. Modifying the byte code interpreter to depend as little as possible on the compiler-time objects (var type needs the compile-time type objects to discriminate between stored values properly - hence the issue in 1. above). The byte code interpreter is pretty free of dependencies at this point. 3. Creating code to write an image file of the compiled output and then load that image and run it. As of this morning, I got the image to load and execute a few dozen byte codes. Checking the instructions executed against what they should be doing reveals that there is a bug I already knew about in how strings are stored in the image. Basically they arent, at least not anywhere near correctly. As far as I know, the only bugs in image files is the handling of string literals and vtable pointers in static objects (and Im not sure whether any static objects in the compiler depend on that feature). In other words, Im within sight of being done with the C++ Parasol compiler!
Posted on: Sat, 09 Nov 2013 18:48:41 +0000
Trending Topics
Recently Viewed Topics
© 2015