Contains the target architecture name:
-"x86", "x64", "arm", "arm64", "ppc", "mips" or "mips64".
+"x86", "x64", "arm", "arm64", "arm64be", "ppc", "mips", "mipsel", "mips64", "mips64el", "mips64r6", "mips64r6el".
-MIPS32
MIPS64 |
+MIPS32
MIPS64
MIPS64r6 |
GCC 4.3+ |
GCC 4.3+ |
|
@@ -177,7 +177,7 @@ Please check the note about the
bytecode format differences, too.
-POSIX Systems (Linux, OSX, *BSD etc.)
+POSIX Systems (Linux, macOS, *BSD etc.)
Prerequisites
Depending on your distribution, you may need to install a package for
@@ -185,14 +185,15 @@ GCC, the development headers and/or a complete SDK. E.g. on a current
Debian/Ubuntu, install libc6-dev with the package manager.
-Download the current source package of LuaJIT (pick the .tar.gz),
-if you haven't already done so. Move it to a directory of your choice,
+The recommended way to fetch the latest version is to do a pull from
+the git repository. Alternatively download the latest source package of
+LuaJIT (pick the .tar.gz). Move it to a directory of your choice,
open a terminal window and change to this directory. Now unpack the archive
and change to the newly created directory:
-tar zxf LuaJIT-2.0.5.tar.gz
-cd LuaJIT-2.0.5
+tar zxf LuaJIT-2.1.0-beta3.tar.gz
+cd LuaJIT-2.1.0-beta3
Building LuaJIT
The supplied Makefiles try to auto-detect the settings needed for your
@@ -216,7 +217,7 @@ You can add an extra prefix to the search paths by appending the
make PREFIX=/home/myself/lj2
-Note for OSX: you must set the MACOSX_DEPLOYMENT_TARGET
+Note for macOS: you must set the MACOSX_DEPLOYMENT_TARGET
environment variable to a value supported by your toolchain.
Installing LuaJIT
@@ -250,8 +251,9 @@ GCC plus the required development headers.
Or install Microsoft's Visual Studio (MSVC).
-Next, download the source package and unpack it using an archive manager
-(e.g. the Windows Explorer) to a directory of your choice.
+Next, pull from the git repository or download the source package and
+unpack it using an archive manager (e.g. the Windows Explorer) to
+a directory of your choice.
Building with MSVC
@@ -269,8 +271,8 @@ Then follow the installation instructions below.
Building with MinGW or Cygwin
Open a command prompt window and make sure the MinGW or Cygwin programs
-are in your path. Then cd to the directory where
-you've unpacked the sources and run this command for MinGW:
+are in your path. Then cd to the directory of the git repository
+or where you've unpacked the sources. Then run this command for MinGW:
mingw32-make
@@ -325,7 +327,7 @@ You need to specify TARGET_SYS whenever the host OS and the
target OS differ, or you'll get assembler or linker errors:
-- E.g. if you're compiling on a Windows or OSX host for embedded Linux or Android, you need to add TARGET_SYS=Linux to the examples below.
+- E.g. if you're compiling on a Windows or macOS host for embedded Linux or Android, you need to add TARGET_SYS=Linux to the examples below.
- For a minimal target OS, you may need to disable the built-in allocator in src/Makefile and use TARGET_SYS=Other.
- Don't forget to specify the same TARGET_SYS for the install step, too.
@@ -522,14 +524,6 @@ the DLL). You may link LuaJIT statically on Windows only if you don't
intend to load Lua/C modules at runtime.
-
-If you're building a 64 bit application on OSX which links directly or
-indirectly against LuaJIT which is not built for LJ_GC64 mode,
-you need to link your main executable with these flags:
-
--pagezero_size 10000 -image_base 100000000
-
-
Additional hints for initializing LuaJIT using the C API functions:
@@ -538,7 +532,7 @@ you need to link your main executable with these flags:
for embedding Lua or LuaJIT into your application.
- Make sure you use luaL_newstate. Avoid using
lua_newstate, since this uses the (slower) default memory
-allocator from your system (no support for this on x64).
+allocator from your system (no support for this on 64 bit architectures).
- Make sure you use luaL_openlibs and not the old Lua 5.0 style
of calling luaopen_base etc. directly.
- To change or extend the list of standard libraries to load, copy
diff --git a/doc/luajit.html b/doc/luajit.html
index ab768053..dd50674d 100644
--- a/doc/luajit.html
+++ b/doc/luajit.html
@@ -154,7 +154,7 @@ LuaJIT is Copyright © 2005-2020 Mike Pall, released under the
Compatibility
-| Windows | Linux | BSD | OSX | POSIX |
+| Windows | Linux | BSD | macOS | POSIX |
| Embedded | Android | iOS |
diff --git a/doc/running.html b/doc/running.html
index f34f1f5f..686d8d90 100644
--- a/doc/running.html
+++ b/doc/running.html
@@ -183,7 +183,7 @@ itself. For a description of their options and output format, please
read the comment block at the start of their source.
They can be found in the lib directory of the source
distribution or installed under the jit directory. By default
-this is /usr/local/share/luajit-2.0.5/jit on POSIX
+this is /usr/local/share/luajit-2.1.0-beta3/jit on POSIX
systems.
diff --git a/doc/status.html b/doc/status.html
index fd0ae8ba..1a8c473c 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -58,9 +58,15 @@ ul li { padding-bottom: 0.3em; }
-LuaJIT 2.0 is the current
-stable branch. This branch is in
-feature-freeze — new features will only be added to LuaJIT 2.1.
+This documentation is for LuaJIT 2.1.0-beta3. Please check the doc
+directory in each git branch for the version-specific documentation.
+
+
+The currently developed branches are LuaJIT 2.1 and LuaJIT 2.0.
+
+
+LuaJIT 2.0 is in feature-freeze — new features will only
+be added to LuaJIT 2.1.
Current Status
@@ -88,8 +94,7 @@ in LuaJIT (no per-coroutine hooks, no tail call counting).
Currently some
out-of-memory errors from
on-trace code are not
handled correctly. The error may fall through an on-trace
pcall or it may be passed on to the function set with
-
lua_atpanic on x64. This issue will be fixed with the new
-garbage collector.
+
lua_atpanic on x64.