在这种情况下会增加编译时间。
在这种环境中要想获得较短的编译时间是极具挑战性的。
And obtaining short compile times in these environments can be a challenge.
但是，时间一久，编译时间上的微小差异也会累积成明显的差异。
Over a long period of time, though, even a smallish difference in compile times adds up.
为了合理的编译时间起见，请只使用需要的参数数量。
For the sake of rational compile times, only use as many arguments as you need.
在前两种情况下，有时必须耗费大量的编译时间才行；
The former two possibilities sometimes necessitate a good deal of compilation time;
本文前面所概述的附加编译时间检查将使得这种复查值得付出努力。
The additional compile time checks outlined earlier in this article will make the review worth the effort.
而复杂的编译优化算法需要耗费大量的编译时间和资源。
But too complex and aggressive optimization algorithm will cost much compilation time and resources.
在团队环境中使用这些工具时，您每天就可以节省几个小时的编译时间。
And when using these tools in a team environment, you could save hours every day just in compile times.
更快的工作站、增加的编辑和可选择的编译器可以使得编译时间更加短暂。
Faster workstations, incremental compilation, and alternative compilers are all strategies that may be used to keep compile times short.
组合使用ccache和distcc，您可以更进一步地改进编译时间。
You can improve compile times even more when using ccache in combination with distcc.
通过对这些机器进行计时，我得知编译时间缩短了9秒，速度提高了大约16倍。
Timing these over those machines tells me this takes just short of 9 seconds to compile, which is around a sixteen-times speed increase.
我很高兴能对这种方法，我希望你会太，因为结婚编译时间验证的运行性能。
I'm excited about this approach, and I hope you will be too, because it marries compile time verification with runtime performance.
随着优化级别的提高，编译源代码所用的编译时间和系统资源增加，而性能的提升幅度下降。
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.
否则将会导致一个编译时间错误，如 “该嵌套类型Person无法隐藏封闭类型”。
You will have a compile-time error something like: "The nested type Person cannot hide an enclosing type".
如果您创建了许多MQT(所有这些MQT都可以用于满足查询)，那么查询的编译时间会增加。
If you have created many MQTs, all of which can be used to satisfy a query, the compilation time of the query can increase.
对于memwatch，您需要添加包含文件memwatch . h并打开两个编译时间标记。
With memwatch, you need to add the include file memwatch.h and turn on two compile time flags.
例如，当你修改版本信息、运行时设置、资源文件、图标/启动画面等时，它会极大地降低编译时间。
It dramatically reduces compilation time if, for example, you modify version info, runtime settings, resource files, icon/splash screen, etc.
在大部分情况下，你会想要去哦去提供编译时间相关的选项的基本的命令来调整你的程序。
In most cases, you will want to supplement the basic commands above with compile-time options appropriate for your application.
JIT编译器将选择它要编译的代码，这样它花费的编译时间很可能通过对代码性能的改进得到补偿。
The JIT compiler is selective about which code it compiles so that the time it takes to do the compilation is likely to be made up by the improvements to the code's performance.
通过在该类型中包括数组大小，编译时间检测器可以象征性地分析数组的存取，确保所有存取都在数组范围内进行。
By including the size in the type, a compile-time checker can symbolically analyze the accesses to the array to ensure that no accesses are done outside the bounds of the array.
通过简单地接触（touch）主要Perl源文件目录中的C 源文件，得到了表1中的重新编译时间。
The recompile times in Table 1 are based on simply doing a touch on each of the C source files in the main Perl source directory.
根据编译时间和编译代码比解释代码快的程度，即使对迭代数量只做很小的变化，也可能造成测量的“性能”有极大差异。
Depending on the compilation time and how much faster the compiled code is than the interpreted code, small changes in the number of iterations can result in big differences in measured "performance."
但有一个警告：启用优化意味着要增加编译时间——编译器尝试去做一些智能的事情，例如追随循环并分析出常量。
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.
但是，如果您的确需要编译，可以告知gwt只针对一个浏览器(用于测试的任何浏览器)进行编译，从而极大地降低编译时间。
However, if you need to compile, you can greatly reduce the compile time by telling GWT to only compile for one browser (whatever browser you like to use for testing.)
如果编译在20,000次迭代时发生，那么总时间会是20,000次解释迭代，加上编译时间，再加上180,000次编译迭代(时间线(c))。
If it kicks in at 20,000 iterations, it will be 20,000 interpreted iterations, plus compilation time, plus 180,000 compiled iterations (timeline (c)).
其中包括使用普通gcc、ccache + gcc、ccache +distcc + gcc所需的编译时间，编译在一个四节点网络中进行并选用了不同的并发distcc作业数目值。
I've included The Times for building with plain GCC, ccache + GCC, and ccache + distcc + GCC in a four-node network with various values of concurrent distcc jobs.
度量应用程序需要多大开销的两个有用的统计信息是JIT编译次数和执行这些编译花费的时间总量。
Two useful statistics for measuring how much overhead your application will encounter are the number of JIT compiles and the total amount of time spent performing these compilations.
随着编译方法的增多及JIT执行编译所需时间的缩短，性能曲线逐渐升高最后达到性能峰值。
As more methods are compiled and the JIT spends less time performing compilations, the performance curve grows and finally begins to reach peak performance.
随着编译方法的增多及JIT执行编译所需时间的缩短，性能曲线逐渐升高最后达到性能峰值。
As more methods are compiled and the JIT spends less time performing compilations, the performance curve grows and finally begins to reach peak performance.
应用推荐