![]() This fits much better with a framework where you can compile most of your program with a normal compiler, but have a few expressions that you won't know until run-time, which you want to execute with something that approaches optimum execution speed.Īs for the apparent intent of original question, I think the basic point of my original answer still stands: while a JIT compiler can adapt to such things as data that varies from one execution to the next, or even varying dynamically during a single execution, the reality is that this makes relatively little difference at least as a general rule. It accepts an expression which is basically expressed as an EDSL inside your C++ program, and generates actual machine code from that, which you can then execute. Rather, it is a small compiler that you can compile into your C++ program. In particular, it does not accept C or C++ source code, and compile it and execute it. This fits the question somewhat differently. ![]() As such, although technically an answer to the question itself, this doesn't really suit the OP's intent very well.Īnother possibility is NativeJIT. The emphasis here is primarily on convenience and fast compiling, not maximum optimization. That is, you give it some source code, give a command for it to run, and it runs. Yes, there are a couple of JIT compilers for C and/or C++.ĬLing (as you might guess from the name) is based on Clang/LLVM.
0 Comments
Leave a Reply. |