> CJIT is not a tracing or adaptive JIT in the VM sense. It does not interpret first and optimize hot paths later.
> CJIT uses TinyCC to compile C quickly, often in memory, and can execute the resulting code immediately.
Wait, what's the difference between this and just using tinycc directly?
cat program.c | tcc -run -
Happy to be proven wrong here, since the project has been around for a couple years. It doesn't appear to just be a random AI one-shot thing.You may be disappointed by the FAQ then https://dyne.org/cjit/faq.html (other than it really isn't an AI thing).
Julia uses a model similar to this. The main advantage is that you can interact much more easily if you have a REPL running where you can do things (assign variables load data etc) and then define/try out new code on that data.