那么JIT编译器就启用了。
JIT compiler to accelerate running Ruby code.
加速Ruby代码运行速度的JIT编译器。
A JIT compiler would see an optimization opportunity here.
JIT编译器会在这里看到一个优化的机会。
Yet a third source of delays within the JVM itself is the JIT compiler.
JVM 中的第三个延迟来源是JIT编译器。
Default JIT compilation, whereby the JIT compiler thread runs at low priority.
默认JIT编译，JIT编译器线程在较低优先级上运行。
This mode enables the JIT compiler to omit optimizations.
此模式使JIT编译器能够忽略优化。
The JiT compiler creates that factory class on the fly, in memory, in the browser.
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编译器是不可接受的。
An example mentioned in the article is NVidia graphics driver which contains a JIT compiler.
在文章中提到的一个例子是NVidia显示驱动，其中包含有JIT编译器。
The IBM JIT compiler USES a sequence of expression trees to represent the method's operations.
IBMJIT编译器使用一个表达式树序列表示方法的操作。
Performance with a JIT compiler is initially very low because methods are initially interpreted.
使用JIT编译器的初始阶段性能很低，因为要首先解释方法。
Reducing the length of these methods can make them more amenable to optimization by a JIT compiler.
而缩短这些方法的长度有助于使JIT编译器更易于优化它们。
If the JIT compiler inlines the accessor, it must JIT that code when the containing method is called.
如果JIT编译器内联了该属性访问符，那么，当包含的方法被调用时，就必须JIT那些代码。
Also, don't forget that in Android 2.2, a JIT compiler will improve the performance of such code as well.
还有，别忘了在Android 2.2中，JIT编译器会提高类似代码的效率。
When it finds an opportunity it will direct a JIT compiler to recompile the section of the code in question.
当找到机会后，它会要求JIT编译器重新编译问题中的某段代码。
The JIT compiler may produce incorrect code that either references or attempts to branch to an invalid location.
JIT编译器可能生成错误代码，该代码引用或尝试对无效的位置进行分支。
More importantly, the code generated by the JIT compiler is bound to the process that triggered the compilation.
更为重要的是，由JIT编译器生成的代码会绑定到触发编译的进程上。
You can run a program that instructs the JIT compiler to turn off all JIT optimizations to produce debuggable code.
您可以运行一个程序来指示JIT编译器禁用所有 JIT优化以产生可调试的代码。
For the OpenJDK the release includes a new JIT compiler, their Pauseless Garbage Collector, and their scalable runtime.
对于OpenJDK来说，该发布包含了一个新的JIT编译器，不会停顿的垃圾收集器和可伸缩的运行时。
But the activity of the JIT compiler itself isn't the only source of unexpected variations in application-level timings.
但是JIT编译器本身的行为并不是应用程序计时中的意外偏差的唯一来源。
Dynamic class loading, which is a challenge for the dynamic JIT compiler, is an even more significant issue for AOT compilation.
动态类加载是动态jit编译器面临的一个挑战，也是AOT编译的一个更重要的问题。
The AOT-compiled code is the equivalent to the native code the JIT compiler would generate if it used a fixed optimisation level.
如果JIT使用了一种固定的优化级别，那么AOT编译的代码就等同于JIT编译器生成的本地代码。
The JIT compiler continues to process MSIL at the new address until it encounters another metadata token and the process is repeated.
JIT编译器继续在新地址处理MSIL，直到它遇到另一个元数据标记，之后，重复该过程。
In a JVM with AOT-compiled code but no JIT compiler, the number of transitions is determined by the set of methods that were compiled into the JXEs.
在具有AOT编译代码而没有JIT编译器的JVM中，转换次数是由被编译到JXE中的方法决定的。
In order for the JIT compiler to determine the correct processor type, system configuration information is examined with the systemcfg_init function.
为了让JIT编译器可以确定正确的处理器类型，需要使用systemcfg_init函数检查系统配置信息。
In an RT environment, however, the JIT compiler introduces an unpredictable run-time behaviour that wreaks havoc on worst-case execution time analysis.
然而，在RT环境中，JIT编译器引入了不可预知的运行时行为，这将严重影响最坏情况时执行时间分析。
In addition, you do not always know which JVMs your code will run on, and the JIT compiler could always change to generate code that breaks this idiom.
此外，您并不总能知道代码会在哪些JVM上运行，而JIT编译器总是会发生变化，从而生成破坏此习语的代码。
The recent performance improvements due to the introduction of the JIT compiler help a lot running Flash applications which are known to be CPU intensive.
最近，JIT编译器的引入极大地改进了性能，这对Flash应用的运行起到了巨大的帮助作用，因为大家都知道，Flash应用是一种CPU密集型应用。
AOT-compiled code, on the other hand, starts much higher than interpreted performance but is unlikely to be as high as can be achieved via the JIT compiler.
另一方面，AOT编译代码启动时的性能比解释的性能高很多，但是无法达到JIT编译器所能达到的最高性能。
应用推荐