IT first shows JIT compilations.
它首先展示了JIT编译。
The Just-in- time (JIT) compiler
即时（Just-in-time，JIT）编译器
First, write a good optimizing JIT.
首先，编写一个好的优化JIT。
那么JIT编译器就启用了。
Enable block inlining within the jit.
在JIT中可以使用block内嵌(block inlining)功能。
Dealing with a JIT related problem.
处理与JIT有关的问题。
The role of the C + + and JIT optimizer.
C++和JIT优化器的作用。
Determining if this is a JIT problem.
确定是否是JIT问题。
JIT compiler to accelerate running Ruby code.
加速Ruby代码运行速度的JIT编译器。
Not all JIT compilers generate the code as above.
不是所有的JIT编译器都生成如上代码。
See Resources for more details on JIT compilation.
有关 JIT 编译的更多详细信息，请参阅 参考资料。
A JIT compiler would see an optimization opportunity here.
JIT编译器会在这里看到一个优化的机会。
JIT debugging is usually a complex and time-consuming procedure.
JIT调试通常是一个复杂而且耗时的过程。
One of these is the activity of the Just-in-time (JIT) compiler.
其中之一就是即时(JIT)编译器的活动。
JIT is the most important JVM component in terms of performance.
就性能而言，JIT是最重要的JVM组件。
To my knowledge, no perfect way to detect JIT compilation exists.
根据我的知识，还没有探测JIT编译是否发生的完美方法。
The JIT approach seemed promising, but it had some drawbacks.
JIT技术看起来很有前途，但是它有一些不足。
JIT improvements are our other main tool for improving performance.
JIT的改进是另一个改善性能的主要工具。
Run the program again to see if problem reappears with JIT disabled.
再次运行一下程序，看一下禁用JIT之后问题是否重现。
The JVM performs JIT compilation of byte code into machine code.
JVM可将字节代码即时编译为机器代码。
The previous section introduced JIT that is an essential part of IBM JVM.
上一节简要介绍了JIT，它是IBM JVM的一个基本部分。
It also holds activation frames for JIT compiled code (with a twist).
它掌握所有JIT编译后代码的活动帧。
We also believed that LLVM was a more robust JIT than it turned out to be.
我们也坚信LLVM是一个更加健壮的JIT，起码比现在看起来应该健壮很多。
Instead, the code is either interpreted or dynamically compiled by the JIT.
相反，这些代码将会由JIT解释或动态编译。
However those restriction quickly melt away if the lock can been JIT 'ed away.
然而，如果锁已经被JIT化了，那么这些限制很快就会消失。
Default JIT compilation, whereby the JIT compiler thread runs at low priority.
默认JIT编译，JIT编译器线程在较低优先级上运行。
Once the method is compiled, the next call to the method runs the JIT compiled version.
方法编译之后，对方法的下一次调用会运行JIT编译的版本。
The last line disables the JIT compiler for the remainder of application execution.
最后一行为应用程序的其余执行部分禁用JIT编译器。
In some RT environments, however, even the presence of the JIT compiler is unacceptable.
但是，在一些RT环境中，出现JIT编译器是不可接受的。
This pseudo code is not only possible, but is exactly what happens on some JIT compilers.
这段伪代码不仅是可能的，而且是一些JIT编译器上真实发生的。
应用推荐