-
Notifications
You must be signed in to change notification settings - Fork 8
/
README
83 lines (60 loc) · 3 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
libjit
------
This library in this distribution implements Just-In-Time compilation
functionality. Unlike other JIT's, this one is designed to be independent
of any particular virtual machine bytecode format or language. The hope
is that Free Software projects can get a leg-up on proprietary VM vendors
by using this library rather than spending large amounts of time writing
their own JIT from scratch.
This JIT is also designed to be portable to multiple archictures.
If you run libjit on a machine for which a native code generator is
not yet available, then libjit will fall back to interpreting the code.
This way, you don't need to write your own interpreter for your
bytecode format if you don't want to.
The library is distributed under the terms of the GNU Lesser General
Public License. See the COPYING.LESSER file for details.
The documentation for libjit is in Texinfo format. A general overview
is in "doc/libjit.texi" with the remainder of the function documentation
in the source files themselves.
Building libjit
---------------
To build libjit from a release tarball you will need GNU make, Bison, and
Flex, and it is also highly recommended that you use gcc. To configure,
build, and install, you would do the following:
./configure
make
make install
To build libjit from the repository tree you will also need autotools:
autoconf, automake, and libtool. These tools let you create ./configure
script which is missing in the repository. To run autotools you would
just do the following:
./bootstrap
Compiler notes
--------------
It is highly recommended that you build libjit with gcc and not
some other C compiler, even if you plan to use some other C
compiler to access the library. We make use of a number of gcc
builtins to assist with stack walking, dynamic function calls,
and closures.
It is also recommended that you don't use the "-fomit-frame-pointer"
option when compiling programs that use libjit. Otherwise stack walking
may not work correctly, leading to problems when throwing exceptions.
The configure script for libjit will detect the presence of this
option in CFLAGS and remove it when building libjit itself.
Contacting the authors
----------------------
The primary author is Rhys Weatherley at Southern Storm Software, Pty Ltd.
He can be reached via e-mail at "rweather@southern-storm.com.au". [ This
address is probably not valid anymore. ]
A number of other authors have also contributed to libjit. The current
libjit maintainer is Aleksey Demakov <ademakov@gmail.com>.
Currently it is recommended to obtain libjit source tree from its Savannah
git repository:
git clone git://git.savannah.gnu.org/libjit.git
The latest released version of libjit is severely out of date and its use
is discuraged. Still it can be downloaded from here:
http://ftp.gnu.org/old-gnu/dotgnu/libjit/
Discussions about libjit can be carried out on the libjit mailing list,
"libjit@gnu.org". For details on how to subscribe to the list visit libjit
home page:
http://www.gnu.org/software/libjit/