Luke Gorrie
Luke Gorrie
Related to the question of what RaptorJIT is #235: Who is RaptorJIT for? (and who is RaptorJIT *not* for?) Thoughts?
This is my current work-in-progress branch for porting the bytecode interpreter to C. This is a really key architectural change that's supposed to pave the way for adding new language...
How should RaptorJIT adopt new features? Let's talk about this. Here's a starting braindump... RaptorJIT should "crowdsource" features from the community in much the same way that the Linux kernel...
Capturing an idea from @corsix to solve the register part of the default FFI calling convention being too heavyweight in some situations (#230): Suppose we could declare that certain functions...
Here is an idea to optimize calls to FFI code when we know that the call won't load and/or store C values that might be cached in JIT registers. This...
FFI calls are sometimes too heavyweight. The FFI is efficient, yes, but it is not efficient enough for every situation. Each FFI call requires that all values in caller-save registers...
FOSDEM 2019 is this weekend! I will be attending and I am interested in meeting up with other LuaJIT/RaptorJIT hackers. There are already a bunch of us in the Snabb...
I have started porting the [Studio](https://github.com/studio/studio) tooling onto the next version of the [GToolkit](https://gtoolkit.com/) inspector framework. The new version is *awesome!* The key difference will be to unify the user-interface,...
Lua objects have a `nextgc` chain that links to other objects. I have the feeling there are some complex invariants that apply to this chain and aren't written down. Is...
Proxy issue to link an interesting case study by @alexandergall over at snabbco/snabb#1409.