3 ms·
Enjoying the discussion. Here’s a related paper: https://docplayer.net/137462966-Towards-jit-compilation-for-io-language.html https://docplayer.net/137462966-To
by stevedekorte 4y ago
Enjoying the discussion. Here’s a related paper: https://docplayer.net/137462966-Towards-jit-compilation-for-io-language.html https://docplayer.net/137462966-Towards-jit-compilation-for-...
- JonChesterfield 4y agoI think this is the same paper, docplayer is not looking great on mobile. Will read it, thanks! https://static.csg.ci.i.u-tokyo.ac.jp/papers/10/zakirov-jssst2010.pdf https://static.csg.ci.i.u-tokyo.ac.jp/papers/10/zakirov-jsss... Covers the right sort of thing. It makes a guess at what a function call will be, inlined that guess, and if it turned out to be wrong restarts from the start of the function in the interpreter. Doesn't explicitly call out the function calling convention but guarded inlining has much the same effect. Maybe worth noting that inlining a fexpr is semantically very close to expanding a macro. Identical if symbol renaming is done the same way for each.