Porting the just-in-time compiler to new hardware platforms.
将即时编译器移植到新的硬件平台。
For example, a just-in-time compiler can monitor which code is executed frequently and optimize just that code for speed.
例如，即时编译器可以监测一些被经常执行代码和，同时进行优化以提高速度。
We've always had an ahead-of-time compiler, to produce pre-compiled Ruby code in.class files. But there were a few things missing.
我们一直都有提前编译器，用于以。class文件的形式来生成预编译的Ruby代码。
The key idea is that we find how far an object can escape and how long it can be reachable; these are done by a static-time compiler.
其中关键的想法在于，我们找出一个物件究竟能逃脱到多远，并依此来确定它的生存期上限。这些工作都是由一个静态的编译器来完成。
In fact, I could argue that I would have finished writing a buggy, yet not-well-tested version of the DFA compiler this month if I hadn't spent so much time on automated tests.
事实上，如果不是在自动化测试方面花了大量的时间，我可能认为在这个月本可以编写完一个还有一些错误且没有经过良好测试的DF A编译器的版本。
There is one caveat: turning on the optimization means that the build time increases. The compiler attempts to do clever things, such as following loops and pulling out constants.
但有一个警告：启用优化意味着要增加编译时间——编译器尝试去做一些智能的事情，例如追随循环并分析出常量。
With each higher level of optimization, compile time and systems resources used to compiler the source code increase as the additional amount of performance squeezed out decreases.
随着优化级别的提高，编译源代码所用的编译时间和系统资源增加，而性能的提升幅度下降。
However, the JIT compiler must also carefully balance the time it takes to compile a program because that time adds to the program's execution time.
然而，JIT编译器还必须注意抵消它编译程序消耗的时间，因为这些时间将延长程序的执行时间。
Build time — Part of the standard compile if the OOP compiler has been extended to AOP, or as a post-compile step.
构建时——如果OOP编译器已经扩展到AOP，那么方面编织就是标准编译的一部分，否则就是编译后的步骤。
That means that a lot of possible errors are caught at compile time. If you try to add together a number and a string, the compiler will whine at you.
这就意味着很大一部分错误都可以在编译时被发现，若试图将一个数字和字符串相加，编译器就会报错。
This article explores the fundamental changes in GCC version 4 to show you why-if you haven't switched yet-the time has come to use the compiler standard.
本文探索GCC第4版中的重要变化，展示为什么—如果您还使用GCC的话—现在应该使用这个编译器标准。
With a static compiler that only compiled one class at a time, we'd be out of luck.
对于每次只编译一个类的静态编译器，我们很幸运。
The hard issues of parallelism and the optimizations needed to produce effective code just don't fit into the time available for a single course in compiler construction.
并行性的难题和生成有效代码所需的优化不适合在单个的编译器构造的课程中讲。
You've seen that with static languages, the compiler directly binds an invocation to an implementation at compile time.
在静态语言中，编译器在编译时直接将调用绑定到实现。
First, if compiling takes a significant fraction of Jester's execution time, try a faster compiler.
首先，如果编译在Jester执行时间中占了显著部分，那么请尝试使用一个更快的编译器。
One-time: These include the infrastructure and policy requirements like deciding on a compiler version or setting up a bug tracking database.
一次(One - time)：这类需求包括架构和策略上的需求，像决定编译器的版本或者设置缺陷跟踪数据库等等。
Psyco — to keep it very short — is a just-in-time (JIT) compiler of Python code into (x86) machine code.
Psyco可以保持代码非常简短；它是(x86)机器代码中的一个JITPython代码编译器。
This marker is enforced strongly by the compiler and weakly at run time; that is, the runtime will expose the internals via reflection if asked.
该标记由编译器强制执行，在运行时则不能很好地被执行；即，运行时将通过映像(reflection)公开这些内部内容(如果要求的话)。
Listing 5 is another for/in after compiler transformation, this time without a genericized type.
清单5是另外一个经过编译器转换之后的for/in，这次没有通用化类型。
The compiler doesn't blindly compile everything though I think it can be deployed as an ahead-of-time (AOT) compiler. It kicks in whenever method execution counters trip over some threshold.
虽然我认为可以将编译器部署为AOT（ahead-of-time）编译器，但它其实并不会盲目地编译所有东西，只有当方法执行计数器超过某个阈值时它才会生效。
The compiler provides a built-in function, which is evaluated at compile time, to determine the length of an array (e.g. len (a)).
编译器提供了内建的功能在编译时求得一个数组的长度(如len (a))。
Spring has developed its own aspect-oriented implementation that allows crosscutting logic to be applied to code at run time, rather than through a compiler as with AspectJ.
Spring已经开发了它自己的面向方面的实现，它允许交叉的逻辑在运行时刻被应用到编码中，而不用通过一个像AspectJ的编译程序来实现。
The Just-in- time (JIT) compiler
即时（Just-in-time，JIT）编译器
To avoid spending time on this type of problem, I added another option to try loading the modified classes directly within the binding compiler.
为了避免把时间花在这类问题上，我添加了另外一个选项，尝试直接在绑定编译器内装入修改后的类。
The biggest issue with most of them is that no compiler warnings or run-time errors tell you that the transaction implementation is incorrect.
大多数陷阱最大的问题是，不会有任何编译器警告或运行时错误告诉您事务实现是不正确的。
Likewise with the generics changes — the generic type information is used by the compiler to enforce compile-time safe usage, but the generated bytecode still USES casts everywhere.
比如泛型更改——泛型类型信息——由编译器用于实施编译时安全，但是生成的字节码仍然到处使用强制转换。
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编译器引入了不可预知的运行时行为，这将严重影响最坏情况时执行时间分析。
Native code is compiled (and can be recompiled) by a Just-in-time (JIT) compiler while the application runs, based on which classes and methods are invoked frequently.
本机代码在应用程序运行时由即时(JIT)编译器编译(而且可以重新编译)，基于经常调用的类和方法。
The loop I used here should be a minor defect, because any decent Just-in-time (JIT) compiler will perform loop unrolling, which lessens the impact.
这里使用的循环应该算是一个缺陷，但是影响不大，因为所有即时（JIT）编译器都会执行循环展开，这会降低循环的影响。
Because of its static nature, precompiled code — unlike code generated dynamically by a JIT compiler — can't benefit from further optimisations of frequently used methods over time.
预先编译的代码有着静态的本质——与JIT编译器动态生成的代码不同，因而不可能在经过一段时间后，得益于常用方法的进一步优化。
应用推荐