Indexed by TopGit from live GitHub metadata: openresty/luajit2 has 1.5k stars, written primarily in C. OpenResty's Branch of LuaJIT 2
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
openresty/luajit2 - OpenResty's maintained branch of LuaJIT.
Table of Contents
Name
Description
OpenResty extensions
New Lua APIs
table.isempty
table.isarray
table.nkeys
table.clone
jit.prngstate
thread.exdata
thread.exdata2
New C API
lua_setexdata
lua_getexdata
lua_setexdata2
lua_getexdata2
lua_resetthread
New macros
OPENRESTY_LUAJIT
HAVE_LUA_RESETTHREAD
Optimizations
Updated JIT default parameters
String hashing
Updated bytecode options
New -bL option
Updated -bl option
Miscellaneous
Copyright & License
Description
This is the official OpenResty branch of LuaJIT. It is not to be considered a
fork, since we still regularly synchronize changes from the upstream LuaJIT
project (https://github.com/LuaJIT/LuaJIT).
OpenResty extensions
Additionally to synchronizing upstream changes, we introduce our own changes
which haven't been merged yet (or never will be). This document describes those
changes that are specific to this branch.
New Lua APIs
table.isempty
syntax:res = isempty(tab)
Returns true when the given Lua table contains neither non-nil array elements
nor non-nil key-value pairs, or false otherwise.
local clone = require "table.clone"
local x = {x=12, y={5, 6, 7}}
local y = clone(x)
... use y ...
Note: We observe 7% over-all speedup in the edgelang-fan compiler's
compiling speed whose Lua is generated by the fanlang compiler.
Note bis: Deep cloning is planned to be supported by adding true as a
second argument.
Back to TOC
jit.prngstate
syntax:state = jit.prngstate(state?)
Returns (and optionally sets) the current PRNG state (an array of 8 Lua
numbers with 32-bit integer values) currently used by the JIT compiler.
When the state argument is non-nil, it is expected to be an array of up to 8
unsigned Lua numbers, each with value less than 2**32-1. This will set the
current PRNG state and return the state that was overridden.
Note: For backward compatibility, state argument can also be an unsigned
Lua number less than 2**32-1.
Note: When the state argument is an array and less than 8 numbers, or the
state is a number, the remaining positions are filled with zeros.
Usage:
local state = jit.prngstate()
local oldstate = jit.prngstate{ a, b, c, ... }
jit.prngstate(32) -- {32, 0, 0, 0, 0, 0, 0, 0}
jit.prngstate{432, 23, 50} -- {432, 23, 50, 0, 0, 0, 0, 0}
Note: This API has no effect if LuaJIT is compiled with
-DLUAJIT_DISABLE_JIT, and will return a table with all 0.
Back to TOC
thread.exdata
syntax:exdata = th_exdata(data?)
This API allows for embedding user data into a thread (lua_State).
The retrieved exdata value on the Lua land is represented as a cdata object
of the ctype void*.
As of this version, retrieving the exdata (i.e. th_exdata() without any
argument) can be JIT compiled.
Usage:
local th_exdata = require "thread.exdata"
th_exdata(0xdeadbeefLL) -- set the exdata of the current Lua thread
local exdata = th_exdata() -- fetch the exdata of the current Lua thread
Also available are the following public C API functions for manipulating
exdata on the C land:
The exdata pointer is initialized to NULL when the main thread is created.
Any child Lua thread will inherit its parent's exdata, but still can override
it.
Note: This API will not be available if LuaJIT is compiled with
-DLUAJIT_DISABLE_FFI.
Note bis: This API is used internally by the OpenResty core, and it is
strongly discouraged to use it yourself in the context of OpenResty.
Back to TOC
thread.exdata2
syntax:exdata = th_exdata2(data?)
Similar to thread.exdata but for a 2nd separate user data as a pointer value.
Back to TOC
New C API
lua_setexdata
void lua_setexdata(lua_State *L, void *exdata);
Sets extra user data as a pointer value to the current Lua state or thread.
Back to TOC
lua_getexdata
void *lua_getexdata(lua_State *L);
Gets extra user data as a pointer value to the current Lua state or thread.
Back to TOC
lua_setexdata2
void lua_setexdata2(lua_State *L, void *exdata2);
Similar to lua_setexdata but for a 2nd user data (pointer) value.
Back to TOC
lua_getexdata2
void *lua_getexdata2(lua_State *L);
Similar to lua_getexdata but for a 2nd user data (pointer) value.
Resets the state of th to the initial state of a newly created Lua thread
object as returned by lua_newthread(). This is mainly for Lua thread
recycling. Lua threads in arbitrary states (like yielded or errored) can be
reset properly.
The current implementation does not shrink the already allocated Lua stack
though. It only clears it.
Back to TOC
New macros
The macros described in this section have been added to this branch.
Back to TOC
OPENRESTY_LUAJIT
In the luajit.h header file, a new macro OPENRESTY_LUAJIT was defined to
help distinguishing this OpenResty-specific branch of LuaJIT.
HAVE_LUA_RESETTHREAD
This macro is set when the lua_resetthread C API is present.
Back to TOC
Optimizations
Updated JIT default parameters
We use more appressive default JIT compiler options to help large OpenResty
Lua applications.
The following jit.opt options are used by default:
maxtrace=8000
maxrecord=16000
minstitch=3
maxmcode=40960 -- in KB
Back to TOC
String hashing
This optimization only applies to Intel CPUs supporting the SSE 4.2 instruction
sets. For such CPUs, and when this branch is compiled with -msse4.2, the
string hashing function used for strings interning will be based on an
optimized crc32 implementation (see lj_str_new()).
This optimization still provides constant-time hashing complexity (O(n)), but
makes hash collision attacks harder for strings up to 127 bytes of size.
Back to TOC
Updated bytecode options
New -bL option
The bytecode option L was added to display Lua sources line numbers.
For example, luajit -bL -e 'print(1)' now produces bytecode dumps like below:
Increased the maximum number of allowed upvalues from 60 to 120.
Various important bugfixes in the JIT compiler and Lua VM which have
not been merged in upstream LuaJIT.
Removed the GCC 4 requirement for x86 on older systems such as Solaris i386.
In the Makefile file, make sure we always install the symlink for "luajit"
even for alpha or beta versions.
Applied a patch to fix DragonFlyBSD compatibility. Note: this is not an
officially supported target.
feature: jit.dump: output Lua source location after every BC.
feature: added internal memory-buffer-based trace entry/exit/start-recording
event logging, mainly for debugging bugs in the JIT compiler. it requires
-DLUA_USE_TRACE_LOGS when building LuaJIT.
feature: save g->jit_base to g->saved_jit_base before lj_err_throw
clears g->jit_base which makes it impossible to get Lua backtrace in such
states.
Back to TOC
Copyright & License
LuaJIT is a Just-In-Time (JIT) compiler for the Lua programming language.
Project Homepage: http://luajit.org/
LuaJIT is Copyright (C) 2005-2019 Mike Pall.
Additional patches for OpenResty are copyrighted by Yichun Zhang and OpenResty
Inc.:
Copyright (C) 2017-2019 Yichun Zhang. All rights reserved.
Copyright (C) 2017-2019 OpenResty Inc. All rights reserved.
LuaJIT is free software, released under the MIT license.
See full Copyright Notice in the COPYRIGHT file or in luajit.h.
Documentation for the official LuaJIT is available in HTML format.
Please point your favorite browser to:
TopGit's last sync did not record any GitHub topics for openresty/luajit2. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on openresty/luajit2?
The most recent commit recorded on openresty/luajit2 was 18 days ago, based on the GitHub push timestamp. The repository has 252 forks — one of the better signals of community interest.
How many stars does openresty/luajit2 have?
openresty/luajit2 has 1.5k GitHub stars — refresh the page for the live number, or check github.com/openresty/luajit2. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is openresty/luajit2 open source?
TopGit's metadata for openresty/luajit2 does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
Where can I see openresty/luajit2 in action?
The project maintains a homepage at https://luajit.org/luajit.html. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about openresty/luajit2?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/openresty/luajit2 is the definitive source.
Read full README in the tab above.
Still deciding about luajit2?
One click hands the question to an AI along with this page — see what it says about luajit2.