1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
5 <meta http-equiv=
"Content-Type" content=
"text/html; charset=iso-8859-1">
6 <meta name=
"Copyright" content=
"Copyright (C) 2005-2022">
7 <meta name=
"Language" content=
"en">
8 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad.css" media=
"screen">
9 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad-print.css" media=
"print">
10 <style type=
"text/css">
11 ul li
{ padding-bottom: 0.3em; }
16 <a href=
"https://luajit.org"><span>Lua
<span id=
"logo">JIT
</span></span></a>
23 <a href=
"luajit.html">LuaJIT
</a>
25 <a href=
"https://luajit.org/download.html">Download
<span class=
"ext">»</span></a>
27 <a href=
"install.html">Installation
</a>
29 <a href=
"running.html">Running
</a>
32 <a href=
"extensions.html">Extensions
</a>
34 <a href=
"ext_ffi.html">FFI Library
</a>
36 <a href=
"ext_ffi_tutorial.html">FFI Tutorial
</a>
38 <a href=
"ext_ffi_api.html">ffi.* API
</a>
40 <a href=
"ext_ffi_semantics.html">FFI Semantics
</a>
43 <a href=
"ext_jit.html">jit.* Library
</a>
45 <a href=
"ext_c_api.html">Lua/C API
</a>
48 <a class=
"current" href=
"status.html">Status
</a>
50 <a href=
"faq.html">FAQ
</a>
52 <a href=
"http://wiki.luajit.org/">Wiki
<span class=
"ext">»</span></a>
54 <a href=
"https://luajit.org/list.html">Mailing List
<span class=
"ext">»</span></a>
59 This documentation is for LuaJIT
2.0.5. Please check the
<tt>doc
</tt>
60 directory in each git branch for the version-specific documentation.
63 The currently developed branches are LuaJIT
2.1 and LuaJIT
2.0.
66 LuaJIT
2.0 is in feature-freeze
— new features will only
67 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 Currently some
<b>out-of-memory
</b> errors from
<b>on-trace code
</b> are not
93 handled correctly. The error may fall through an on-trace
94 <tt>pcall
</tt> or it may be passed on to the function set with
95 <tt>lua_atpanic
</tt> on x64.
102 Copyright
© 2005-
2022
103 <span class=
"noprint">
105 <a href=
"contact.html">Contact
</a>