Get the latest tech news
JIT-ing a stack machine (with SLJIT)
From bytebeat to JITRecently, I got nerdsniped with bytebeat.I made a simple program for editting it live with visual...
This is by far the optimization with the higest gain to effort ratio: Just by switching internal calling convention and writing a wrapper, we eliminated a lot of register saving/spilling and memory accesses. We have not only eliminated a lot of memory access but the generated code is also smaller, potentially fit into the instruction cache better in the case of loops. There is nothing advanced about it but the combination of the two modes and the possibility of cache miss and spill creates a lot of branches (in the compiler, not the generated code).
Or read this on Hacker News
