4 ms·
Well, this is the perfect case for jits: basic number crunching. Bytecode interpreters are pure overhead in this case. Problems usually come from jumping betwe
by vkazanov 8y ago
Well, this is the perfect case for jits: basic number crunching. Bytecode interpreters are pure overhead in this case.
Problems usually come from jumping between jitted/non-jitted code or, say, pointer chasing in complex objects.
Did you find any use for the libjit wrapper? is it usable practically?
- UncleEntity 8y ago> Did you find any use for the libjit wrapper? is it usable practically? Other than it starting me off on a multi-year dive down the compiler/interpreter rabbit hole I didn't do too much with it since I didn't really have the knowledge to use it at the time. I also want to rewrite it because the C++ libjit API is kind of wonky and it really should be using the C-API but haven't gotten around to it yet. Someday I'll get motivated and work on it again, have a couple half finished projects that could use it as a back end if I ever get around to finishing them.