Minor changes.
git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@1841 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
parent
740d2d2e41
commit
ae7d5cbe71
@ -1278,15 +1278,16 @@ perform code optimizations during runtime and our feeling is that LP
|
|||||||
implementation has been left a bit behind times. We hold that this
|
implementation has been left a bit behind times. We hold that this
|
||||||
should change.
|
should change.
|
||||||
%
|
%
|
||||||
Indeed, we see \JITI as only the first, albeit a very important, step
|
Indeed, we see \JITI as only the first, albeit very important, step
|
||||||
towards effective runtime optimization of logic programs.
|
towards effective runtime optimization of logic programs.
|
||||||
|
|
||||||
As presented, \JITI is a hybrid technique: index generation occurs
|
As presented, \JITI is a hybrid technique: index generation occurs
|
||||||
during runtime but is partly guided by the compiler, because we want
|
during runtime but is partly guided by the compiler, because we want
|
||||||
to preserve compile-time WAM-style indexing. More flexible schemes are
|
to combine it with compile-time WAM-style indexing. More flexible
|
||||||
possible. For example, index generation can be fully dynamic (as in
|
schemes are of course possible. For example, index generation can be
|
||||||
YAP), combined with user declarations, or use static analysis to be
|
fully dynamic (as in YAP), combined with user declarations, or use
|
||||||
even more selective or go beyond fixed-order indexing.
|
static analysis to be even more selective or go beyond fixed-order
|
||||||
|
indexing.
|
||||||
%
|
%
|
||||||
Finally, note that \JITI fully respects Prolog semantics. Better
|
Finally, note that \JITI fully respects Prolog semantics. Better
|
||||||
performance can be achieved in the context of one solution
|
performance can be achieved in the context of one solution
|
||||||
|
Reference in New Issue
Block a user