Lofty

So, this seems to be for exactly 64-bit integers; [32-bit integers already have this optimisation](https://github.com/raptorjit/raptorjit/blob/master/src/lj_opt_fold.c#L236). Makes one wonder why Mike didn't include it.

Actually the optimisation here is [this one](https://github.com/raptorjit/raptorjit/blob/master/src/lj_opt_fold.c#L1347). Again, though, this optimisation doesn't apply for 64-bit math.

I think RaptorJIT needs a new garbage collector because the current one is not thread safe, making it a blocker on internal multi-threading. I would be in favour of a...

Could you be more specific with that? While pointer moving does result in indirection, since the VM uses NaN-tagging, pointers are usually pretty obvious, and can be patched in a...

For what it's worth, I'm torn on this. "Embedding the binary blob" is not a trivial task here - I think it would involve linker scripts or being dumped into...

> What? I'm just suggesting we write lua_load in pure Lua So, suppose somebody else comes along and thinks "this is a good runtime, let's write my language for the...

> it's no more arbitrary than the machine code around it. And no more trustworthy, honestly. > what's your C compiler written in? C++, because C is a bad language...

When you all you have is a hammer, everything looks like a nail. LuaJIT has a pretty good hammer: trace stitching. If the Lua C API is a landmine, then...

The idea is you write your program in RaptorJIT, not to extend a C program. On Tue, 19 Feb 2019, 10:05 Henri D I don't understand if the C-API you...

Given that https://github.com/openresty/lua-nginx-module/blob/master/src/api/ngx_http_lua_api.h includes lua.h, it's probably using the C API. On Tue, 19 Feb 2019, 13:05 Luke Gorrie Related: How does OpenResty integrate with nginx? C-API, FFI, or both?...