Hello, Noah Lavine <noah.b.lav...@gmail.com> skribis:
> I sent another email recently about different ways to make the JITter > understand all of the bytecode, but at the time, I thought I would > have to parse the C definition of the VM and generate the JITter from > that in order for it to be merged into Guile. I never got over that > hurdle. If we are willing to generate both the VM and the JITter from > another source, it's possible that I could revive my old JIT branch. I think it could be beneficial in terms of hackability and maintenance to have instructions defined as slightly abstracted s-exps. Now, if it’s only used to generate vm-engine.c & co., it’s probably too much work for what it’s worth. > However, I'm still not sure if that's the best way there. Having the > assembler written in Scheme gives you an easier path towards > all-Scheme native compilation, which you'd probably want for an AOT > compiler. Yeah, especially since it could easily be used at run-time too. Thanks, Ludo’.
