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.
This API can be JIT compiled.
Usage:
local isempty =require"table.isempty"print(isempty({})) -- trueprint(isempty({nil, dog =nil})) -- trueprint(isempty({"a", "b"})) -- falseprint(isempty({nil, 3})) -- falseprint(isempty({cat =3})) -- false
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.
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 threadlocal 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.
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.
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.
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.
请发表评论