gh-mirror/mikepaul-LuaJIT
1
0
Fork 0
mirror of https://github.com/LuaJIT/LuaJIT.git synced 2025-02-07 15:14:08 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Misc. updates to docs.

Browse Source
This commit is contained in:
Mike Pall 2011-05-05 01:15:22 +02:00
parent 6534152b44
commit b760add618
5 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ext_ffi.html
View File

@ -84,10 +84,10 @@ code a C compiler would generate. Calls to C functions can
be inlined in JIT-compiled code, unlike calls to functions bound via be inlined in JIT-compiled code, unlike calls to functions bound via
the classic Lua/C API. the classic Lua/C API.
</p> </p>
<p> <p><em>
This page gives a short introduction to the usage of the FFI library. This page gives a short introduction to the usage of the FFI library.
Please use the FFI sub-topics in the navigation bar to learn more. <em>Please use the FFI sub-topics in the navigation bar to learn more.</em>
</p> </em></p>
<h2 id="call">Motivating Example: Calling External C Functions</h2> <h2 id="call">Motivating Example: Calling External C Functions</h2>
<p> <p>

2
doc/ext_ffi_semantics.html
View File

@ -80,7 +80,7 @@ applications using the LuaJIT FFI for developers with a C or C++
background. background.
</p> </p>
<p class="indent" style="color: #c00000;"> <p class="indent" style="color: #c00000;">
Please note: this is the first public release of the FFI library. This Please note: this is an early public release of the FFI library. This
does not comprise the final specification for the FFI semantics, yet. does not comprise the final specification for the FFI semantics, yet.
Some of the semantics may need to be changed, based on feedback from Some of the semantics may need to be changed, based on feedback from
developers. Please <a href="contact.html">report</a> any problems you developers. Please <a href="contact.html">report</a> any problems you

7
doc/faq.html
View File

@ -152,9 +152,10 @@ The compiler will happily optimize away such indirections.</dd>
<dd>Because it's a compiler &mdash; it needs to generate native <dd>Because it's a compiler &mdash; it needs to generate native
machine code. This means the code generator must be ported to each machine code. This means the code generator must be ported to each
architecture. And the fast interpreter is written in assembler and architecture. And the fast interpreter is written in assembler and
must be ported, too. This is quite an undertaking.<br> Currently only must be ported, too. This is quite an undertaking.<br>
x86, x64 and PPC/e500v2 CPUs are supported. Other architectures will follow The <a href="install.html">install documentation</a> shows the supported
based on sufficient user demand and/or sponsoring.</dd> architectures. Other architectures will follow based on sufficient user
demand and/or sponsoring.</dd>
</dl> </dl>
<dl> <dl>

3
doc/install.html
View File

@ -484,7 +484,8 @@ overridden, but it's <em>not</em> recommended, except for special needs
like cross-builds: like cross-builds:
<tt>BUILDMODE, CC, HOST_CC, STATIC_CC, DYNAMIC_CC, CFLAGS, HOST_CFLAGS, <tt>BUILDMODE, CC, HOST_CC, STATIC_CC, DYNAMIC_CC, CFLAGS, HOST_CFLAGS,
TARGET_CFLAGS, LDFLAGS, HOST_LDFLAGS, TARGET_LDFLAGS, TARGET_SHLDFLAGS, TARGET_CFLAGS, LDFLAGS, HOST_LDFLAGS, TARGET_LDFLAGS, TARGET_SHLDFLAGS,
LIBS, HOST_LIBS, TARGET_LIBS, CROSS, HOST_SYS, TARGET_SYS</tt></li> TARGET_FLAGS, LIBS, HOST_LIBS, TARGET_LIBS, CROSS, HOST_SYS, TARGET_SYS
</tt></li>
</ul> </ul>
<p> <p>
The build system has a special target for an amalgamated build, i.e. The build system has a special target for an amalgamated build, i.e.

4
doc/luajit.html
View File

@ -79,8 +79,8 @@ standard Lua interpreter and can be deployed as a drop-in replacement.
<p> <p>
LuaJIT offers more performance, at the expense of portability. It LuaJIT offers more performance, at the expense of portability. It
currently runs on all popular operating systems based on currently runs on all popular operating systems based on
<b>x86</b> or <b>x64 CPUs</b> (Linux, Windows, OSX etc.) or embedded Linux <b>x86</b> or <b>x64</b> CPUs (Linux, Windows, OSX etc.) or embedded
systems based on <b>PPC/e500v2 CPUs</b>. systems based on <b>ARM</b> (Android, iOS) or <b>PPC/e500v2</b> CPUs.
Other platforms will be supported in the future, based on user demand Other platforms will be supported in the future, based on user demand
and sponsoring. and sponsoring.
</p> </p>