P98-2133 |
performance evaluations on the
|
native-code compiler
|
are also presented . 5.1 Design
|
P98-2133 |
because the implementation of the
|
native-code compiler
|
is not completed . How - ever
|
P98-2133 |
implementation of built-in functions on the
|
native-code compiler
|
. 5.3 Performance Evaluation
|
P98-2133 |
We are currently developing a
|
native-code compiler
|
of LiLFeS in order to attain
|
P98-2133 |
to Table 3 ) approaches to the
|
native-code compiler
|
versions of commercial Prolog
|
P98-2133 |
Compiler We are developing the LiLFeS
|
native-code compiler
|
in LiLFeS itself . This is because
|
P98-2133 |
design policies for the LiLFeS
|
native-code compiler
|
are : • Native code output
|
P98-2133 |
SICStus ( breadth-first ) and LiLFeS
|
native-code compiler
|
( depth-first ) 5 . What is notable
|
P98-2133 |
Van Roy , 1990 ) , an optimizing
|
native-code compiler
|
for Prolog . Aquarius Prolog
|
P98-2133 |
the performance of the LiLFeS
|
native-code compiler
|
with the same experiments as
|
P98-2133 |
TFSs . We are now developing a
|
native-code compiler
|
version of LiLFeS ; the prototype
|
P98-2133 |
still slower than ProFIT + SICStus
|
native-code compiler
|
in some experiments , though
|
P98-2133 |
and Table 6 . The results of the
|
native-code compiler
|
are significantly better than
|
P07-2053 |
. OCaml has a highperformance
|
native-code compiler
|
( Doligez et al. , 2004 ) that
|
P98-2133 |
this optimized LiLFeS . 5 LiLFeS
|
Native-Code Compiler
|
We are currently developing a
|
P98-2133 |
, while the second one uses a
|
native-code compiler
|
and therefore is much more efficient
|
P98-2133 |
Performance Evaluation of the LiL - FeS
|
Native-Code Compiler
|
We evaluated the performance
|