Luke Gorrie

Results 165 issues of Luke Gorrie

The test suite should run with `lua_assert()` enabled. Bugs caught by assertions need to be fixed.

I have been listening to other people's experiences with LuaJIT lately and I have come upon three (!) new ideas about the bytecode interpreter. This issue is meant as a...

Here is a rough idea for explaining how the JIT chooses which traces to create. Contributing towards #169. Suppose we have already explained what a *trace* is. ### Loops The...

idea

I'm finding it surprisingly hard to log the name of each new ctype when it is created. The purpose is to log a mapping from ctype-id to a useful name...

help wanted
question

We should formulate a short (ten minute) explanation of how the JIT works. Goal is to provide a practical mental model for writing efficient code, understanding how code is traced,...

goal

One major change introduced in LuaJIT GC64 mode is to reserve one register (r14) as `RID_DISPATCH` pointing to the dispatch table. The advantage is this makes it possible to assemble...

idea

I'm learning to make screencasts for RaptorJIT. Here's an early [demo/tutorial video](https://youtu.be/MQyxXSPXcwg) of the [Studio](https://github.com/studio/studio) GUI features for inspecting IR code in RaptorJIT. If you have access to Linux then...

info

I found the blog post [My love-hate relationship with LuaJIT](https://blog.separateconcerns.com/2015-06-18-love-hate-luajit.html) thought provoking. The title is hyperbolic but I can relate to the reflections. He nicely expresses both positive and negative...

goal

RaptorJIT currently supports only x86-64. This is the dominant platform in server networking. However, the world moves forwards and in the future we will want to support more architectures like...

goal

One awesome feature would be for RaptorJIT to bounds-check FFI memory access. This way an off-by-one error that overwrites the end of an array would cause a Lua exception rather...