<ahref="http://luajit.org/list.html">Mailing List <spanclass="ext">»</span></a>
</li></ul>
</div>
<divid="main">
<p>
<spanstyle="color: #0000c0;">LuaJIT 2.0</span> is the current
<spanstyle="color: #0000c0;">stable branch</span>. This branch is in
feature-freeze — new features will only be added to LuaJIT 2.1.
</p>
<h2>Current Status</h2>
<p>
LuaJIT ought to run all Lua 5.1-compatible source code just fine.
It's considered a serious bug if the VM crashes or produces unexpected
results — please report this.
</p>
<p>
Known incompatibilities and issues in LuaJIT 2.0:
</p>
<ul>
<li>
There are some differences in <b>implementation-defined</b> behavior.
These either have a good reason, are arbitrary design choices
or are due to quirks in the VM. The latter cases may get fixed if a
demonstrable need is shown.
</li>
<li>
The Lua <b>debug API</b> is missing a couple of features (return
hooks for non-Lua functions) and shows slightly different behavior
in LuaJIT (no per-coroutine hooks, no tail call counting).
</li>
<li>
Some checks are missing in the JIT-compiled code for obscure situations
with <b>open upvalues aliasing</b> one of the SSA slots later on (or
vice versa). Bonus points, if you can find a real world test case for
this.
</li>
<li>
Currently some <b>out-of-memory</b> errors from <b>on-trace code</b> are not
handled correctly. The error may fall through an on-trace
<tt>pcall</tt> or it may be passed on to the function set with
<tt>lua_atpanic</tt> on x64. This issue will be fixed with the new
garbage collector.
</li>
</ul>
<h2>Roadmap</h2>
<p>
Please refer to the
<ahref="http://www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013"><spanclass="ext">»</span> LuaJIT Roadmap 2012/2013</a> and an
<ahref="http://www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013-UPDATE"><spanclass="ext">»</span> update on release planning</a> for details.