Re:Nash – A tracing JIT compiler for Scheme [pdf]
by sabauma on Saturday March 04, 2017 @02:20PM
(#13792433)
Chez is an AOT compiler. I am not sure how the REPL operates, but I believe it just compiles expression on the fly before executing them. I suppose you could characterize that as JIT compilation, but the optimizer does not make use of any runtime profiling information. Racket's "JIT" is similar in that code is generated for a function when it is first called, but the optimizer is run on the bytecodes of the program before anything is run.
[ Parent
| on HN ]
Re:Nash – A tracing JIT compiler for Scheme [pdf]
by fiddlerwoaroof on Saturday March 04, 2017 @02:48PM
(#13792588)
In Common Lisp it's fairly common for eval to compile the code and then execute it. For example, sbcl's repl usually compiles the entered expression and then executes it: although recent versions also provide an interpreted mode.
Re:Nash – A tracing JIT compiler for Scheme [pdf]
by sedachv on Sunday March 05, 2017 @12:27AM
(#13794736)
> I suppose you could characterize that as JIT compilation, but the optimizer does not make use of any runtime profiling information.
That is JIT compilation. AFAIK James Gosling started using the phrase in the 1990s to pretend that it was something novel and to ignore the fact that that is how Lisp and Smalltalk systems have always worked. This is really confusing today because a lot of people started using "JIT" to be synonymous with dynamic recompilation techniques like tracing.
Re:Nash – A tracing JIT compiler for Scheme [pdf]
by throwaway7645 on Saturday March 04, 2017 @03:17PM
(#13792731)
Ah. So if Racket uses the Chez Compiler it could use it for the REPL as well.