1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
4 <title>Status
& Roadmap
</title>
5 <meta http-equiv=
"Content-Type" content=
"text/html; charset=iso-8859-1">
6 <meta name=
"Author" content=
"Mike Pall">
7 <meta name=
"Copyright" content=
"Copyright (C) 2005-2014, Mike Pall">
8 <meta name=
"Language" content=
"en">
9 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad.css" media=
"screen">
10 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad-print.css" media=
"print">
11 <style type=
"text/css">
12 ul li
{ padding-bottom: 0.3em; }
17 <a href=
"http://luajit.org"><span>Lua
<span id=
"logo">JIT
</span></span></a>
20 <h1>Status
& Roadmap
</h1>
24 <a href=
"luajit.html">LuaJIT
</a>
26 <a href=
"http://luajit.org/download.html">Download
<span class=
"ext">»</span></a>
28 <a href=
"install.html">Installation
</a>
30 <a href=
"running.html">Running
</a>
33 <a href=
"extensions.html">Extensions
</a>
35 <a href=
"ext_ffi.html">FFI Library
</a>
37 <a href=
"ext_ffi_tutorial.html">FFI Tutorial
</a>
39 <a href=
"ext_ffi_api.html">ffi.* API
</a>
41 <a href=
"ext_ffi_semantics.html">FFI Semantics
</a>
44 <a href=
"ext_jit.html">jit.* Library
</a>
46 <a href=
"ext_c_api.html">Lua/C API
</a>
49 <a class=
"current" href=
"status.html">Status
</a>
51 <a href=
"changes.html">Changes
</a>
54 <a href=
"faq.html">FAQ
</a>
56 <a href=
"http://luajit.org/performance.html">Performance
<span class=
"ext">»</span></a>
58 <a href=
"http://wiki.luajit.org/">Wiki
<span class=
"ext">»</span></a>
60 <a href=
"http://luajit.org/list.html">Mailing List
<span class=
"ext">»</span></a>
65 <span style=
"color: #0000c0;">LuaJIT
2.0</span> is the current
66 <span style=
"color: #0000c0;">stable branch
</span>. This branch is in
67 feature-freeze
— new features will only be added to LuaJIT
2.1.
70 <h2>Current Status
</h2>
72 LuaJIT ought to run all Lua
5.1-compatible source code just fine.
73 It's considered a serious bug if the VM crashes or produces unexpected
74 results
— please report this.
77 Known incompatibilities and issues in LuaJIT
2.0:
81 There are some differences in
<b>implementation-defined
</b> behavior.
82 These either have a good reason, are arbitrary design choices
83 or are due to quirks in the VM. The latter cases may get fixed if a
84 demonstrable need is shown.
87 The Lua
<b>debug API
</b> is missing a couple of features (return
88 hooks for non-Lua functions) and shows slightly different behavior
89 in LuaJIT (no per-coroutine hooks, no tail call counting).
92 Some checks are missing in the JIT-compiled code for obscure situations
93 with
<b>open upvalues aliasing
</b> one of the SSA slots later on (or
94 vice versa). Bonus points, if you can find a real world test case for
98 Currently some
<b>out-of-memory
</b> errors from
<b>on-trace code
</b> are not
99 handled correctly. The error may fall through an on-trace
100 <tt>pcall
</tt> or it may be passed on to the function set with
101 <tt>lua_atpanic
</tt> on x64. This issue will be fixed with the new
109 <a href=
"http://www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013"><span class=
"ext">»</span> LuaJIT Roadmap
2012/
2013</a> and an
110 <a href=
"http://www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013-UPDATE"><span class=
"ext">»</span> update on release planning
</a> for details.
118 Copyright
© 2005-
2014 Mike Pall
119 <span class=
"noprint">
121 <a href=
"contact.html">Contact
</a>