LuaJIT
/
LuaJIT
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

RELEASE LuaJIT-2.0.0-beta9

master
Mike Pall 2011-12-14 15:12:49 +01:00
parent a302468345
commit 6ace80c897
10 changed files with 17 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@ -16,7 +16,7 @@
MAJVER= 2
MINVER= 0
RELVER= 0
PREREL= -beta8
PREREL= -beta9
VERSION= $(MAJVER).$(MINVER).$(RELVER)$(PREREL)
ABIVER= 5.1
NODOTABIVER= 51

2
README
View File

@ -1,4 +1,4 @@
README for LuaJIT 2.0.0-beta8
README for LuaJIT 2.0.0-beta9
-----------------------------
LuaJIT is a Just-In-Time (JIT) compiler for the Lua programming language.

2
doc/changes.html
View File

@ -59,7 +59,7 @@ div.major { max-width: 600px; padding: 1em; margin: 1em 0 1em 0; }
<div id="main">
<p>
This is a list of changes between the released versions of LuaJIT.<br>
The current <span style="color: #c00000;">development version</span> is <strong>LuaJIT&nbsp;2.0.0-beta8</strong>.<br>
The current <span style="color: #c00000;">development version</span> is <strong>LuaJIT&nbsp;2.0.0-beta9</strong>.<br>
The current <span style="color: #0000c0;">stable version</span> is <strong>LuaJIT&nbsp;1.1.7</strong>.
</p>
<p>

4
doc/ext_ffi_semantics.html
View File

@ -942,8 +942,8 @@ GUI application, which waits for user input most of the time, anyway.
For new designs <b>avoid push-style APIs</b> (C&nbsp;function repeatedly
calling a callback for each result). Instead <b>use pull-style APIs</b>
(call a C&nbsp;function repeatedly to get a new result). Calls from Lua
to C via the FFI are much faster than the other way round. Most well
designed libraries already use pull-style APIs (read/write, get/put).
to C via the FFI are much faster than the other way round. Most well-designed
libraries already use pull-style APIs (read/write, get/put).
</p>
<h2 id="clib">C Library Namespaces</h2>

8
doc/install.html
View File

@ -178,8 +178,8 @@ open a terminal window and change to this directory. Now unpack the archive
and change to the newly created directory:
</p>
<pre class="code">
tar zxf LuaJIT-2.0.0-beta8.tar.gz
cd LuaJIT-2.0.0-beta8</pre>
tar zxf LuaJIT-2.0.0-beta9.tar.gz
cd LuaJIT-2.0.0-beta9</pre>
<h3>Building LuaJIT</h3>
<p>
The supplied Makefiles try to auto-detect the settings needed for your
@ -229,11 +229,11 @@ Obviously the prefixes given during build and installation need to be the same.
<p style="color: #c00000;">
Note: to avoid overwriting a previous version, the beta test releases
only install the LuaJIT executable under the versioned name (i.e.
<tt>luajit-2.0.0-beta8</tt>). You probably want to create a symlink
<tt>luajit-2.0.0-beta9</tt>). You probably want to create a symlink
for convenience, with a command like this:
</p>
<pre class="code" style="color: #c00000;">
sudo ln -sf luajit-2.0.0-beta8&nbsp;/usr/local/bin/luajit
sudo ln -sf luajit-2.0.0-beta9&nbsp;/usr/local/bin/luajit
</pre>
<h2 id="windows">Windows Systems</h2>

6
doc/running.html
View File

@ -85,11 +85,11 @@ interactive mode, too.
<p class="indent" style="color: #c00000;">
Note: the beta test releases only install under the versioned name on
POSIX systems (to avoid overwriting a previous version). You either need
to type <tt>luajit-2.0.0-beta8</tt> to start it or create a symlink
to type <tt>luajit-2.0.0-beta9</tt> to start it or create a symlink
with a command like this:
</p>
<pre class="code" style="color: #c00000;">
sudo ln -sf luajit-2.0.0-beta8&nbsp;/usr/local/bin/luajit
sudo ln -sf luajit-2.0.0-beta9&nbsp;/usr/local/bin/luajit
</pre>
<p>
Unlike previous versions <b>optimization is turned on by default</b> in
@ -195,7 +195,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 <tt>lib</tt> directory of the source
distribution or installed under the <tt>jit</tt> directory. By default
this is <tt>/usr/local/share/luajit-2.0.0-beta8/jit</tt> on POSIX
this is <tt>/usr/local/share/luajit-2.0.0-beta9/jit</tt> on POSIX
systems.
</p>

4
doc/status.html
View File

@ -148,10 +148,6 @@ with me, before writing major improvements, to avoid duplication of
effort.
</li>
<li>
<b>Trace management</b> needs more tuning: less drastic countermeasures
against trace explosion and better heuristics in general.
</li>
<li>
Some checks are missing in the JIT-compiled code for obscure situations
with <b>open upvalues aliasing</b> one of the SSA slots later on (or
vice versa). Bonus points, if you can find a real world test case for

2
etc/luajit.pc
View File

@ -2,7 +2,7 @@
majver=2
minver=0
relver=0
version=${majver}.${minver}.${relver}-beta8
version=${majver}.${minver}.${relver}-beta9
abiver=5.1
prefix=/usr/local

4
src/luaconf.h
View File

@ -26,12 +26,12 @@
#define LUA_LDIR LUA_ROOT "share/lua/5.1/"
#define LUA_CDIR LUA_ROOT "lib/lua/5.1/"
#ifdef LUA_XROOT
#define LUA_JDIR LUA_XROOT "share/luajit-2.0.0-beta8/"
#define LUA_JDIR LUA_XROOT "share/luajit-2.0.0-beta9/"
#define LUA_XPATH \
";" LUA_XROOT "share/lua/5.1/?.lua;" LUA_XROOT "share/lua/5.1/?/init.lua"
#define LUA_XCPATH LUA_XROOT "lib/lua/5.1/?.so;"
#else
#define LUA_JDIR LUA_ROOT "share/luajit-2.0.0-beta8/"
#define LUA_JDIR LUA_ROOT "share/luajit-2.0.0-beta9/"
#define LUA_XPATH
#define LUA_XCPATH
#endif

4
src/luajit.h
View File

@ -30,9 +30,9 @@
#include "lua.h"
#define LUAJIT_VERSION "LuaJIT 2.0.0-beta8"
#define LUAJIT_VERSION "LuaJIT 2.0.0-beta9"
#define LUAJIT_VERSION_NUM 20000 /* Version 2.0.0 = 02.00.00. */
#define LUAJIT_VERSION_SYM luaJIT_version_2_0_0_beta8
#define LUAJIT_VERSION_SYM luaJIT_version_2_0_0_beta9
#define LUAJIT_COPYRIGHT "Copyright (C) 2005-2011 Mike Pall"
#define LUAJIT_URL "http://luajit.org/"