To be a bit less pedantic, this is an area that is kind of ambiguous... From one point of view it's still fair to call this "just in time".
I wish there was terminology to differentiate between kind of "on demand AOT compilation" and jits that do jitty stuff that can't be done ahead of time.
Re:How to write a simple JIT compiler
by chrisseaton on Wednesday December 15, 2021 @01:38PM
(#29569920)
> I wish there was terminology to differentiate between kind of "on demand AOT compilation" and jits that do jitty stuff that can't be done ahead of time.
Some people differentiate between dynamic JIT compilation and static JIT compilation.
Re:How to write a simple JIT compiler
by adgjlsfhk1 on Wednesday December 15, 2021 @12:39PM
(#29569103)
Julia uses the term just ahead of time for this, which I think fits well.
That strikes me as just-in-time optimization less so than ahead-of-time.
If the code isn't compiled until it's executed, "ahead of time" seems extremely confusing
Arguably the term "ahead of time" also suffers from the same problem. Among compiler people, "ahead of time" vs "just in time" sometimes has to do with whether the compiler uses run-time information when compiling. But the names don't reflect that, they talk about when the compilation happens.
> kind of "on demand AOT compilation"
I assume you mean something like Common Lisp does with COMPILE? (http://clhs.lisp.se/Body/f_cmp.htm) That's just called "compilation" in some circles.
As an example, here's a JIT compiler I made for BrainFuck that defers the compilation of some loops: https://github.com/danthedaniel/BF-JIT/blob/master/src/runna...