如果您编译运行gnu调试器，可能会使用太多内存，或许是因为您进入一个程序呼叫时，它都试图打开一个窗口。
It may use too much memory if you compile and run the GNU debugger, probably because it tends to open a window whenever you step into a program call.
我们需要的是这样一个程序，它可以生成这些结果，并将其输出到上面这样的表中，这样就可以在编译时加载了。
What is needed is a program that will produce these values and print them out in a table like the previous one so they are loaded in at compile-time.
不同平台之间的不兼容性尤其危险，因为它可能会导致程序返回错误结果，而不是编译时错误。
This incompatibility between platforms is particularly dangerous as it might cause programs to return wrong results rather than causing a compile-time error.
在做这些练习时，我们推荐您在自己的系统上下载、编译和运行这些程序。
As you are working through the exercises, you're encouraged to download, compile, and run these programs on your own system.
这个程序在x86和PowerPC 上都可以很好地运行，不过在Power系统上使用-m64选项进行编译时就会死掉。
This program runs fine on both x86 and PowerPC, but dies on the Power system when compiled with the -m64 option.
不幸的是，前面的例子程序调用strcmp时没有给出参数，因此生成的汇编代码无效，从而导致编译失败。
Unfortunately, the sample program called STRCMP with no arguments, so the resulting assembly code was invalid and the compile failed.
在尝试向泛型集合(本例中为List)添加错误类型的元素时，清单2中的程序会生成编译时错误消息。
Listing 2 contains a program that generates the compilation-time error message that happens when you try to add the wrong type of element to a generic collection - a List in this case.
在启动时受程序控制的编译，禁用了重新编译。
Program-controlled compilation at startup with recompilation disabled.
如果在没有事先获得函数指针的情况下直接调用函数(也就是说，编译时静态连接mswsock.lib，在程序中直接调用函数)，那么性能将很受影响。
Calling the function without previously obtaining a function pointer (that is, by linking with mswsock.
当编译器不会改变程序的语义时，作为一种优化它可以随意地重新排序某些指令。
The compiler is free to reorder certain instructions as an optimization when it would not change the semantics of the program.
它设法模块化这些关键点，但是也允许设计良好的和其它关键点行为的“混合”，包括应用程序的核心域逻辑，不管是在编译时还是运行时。
It seeks to modularize these concerns, yet enable the fine-grained "mixing" of their behaviors with other concerns, including the core domain logic of the application, either at build or run time.
但是如果这个驱动程序被编译成一个模块，就只有在需要内存并将其加载到内核时才会真正占用内存空间。
But if the driver is compiled as a module, it requires memory only if memory is needed and subsequently loaded, into the kernel.
与大内存模型类似，可以通过一个链接器选项或在运行时使用LDR_CNTRL环境变量来为编译时的可执行程序启用超大内存模型。
The very large memory model, like the large memory model, can be enabled for an executable at compile time with a linker option or at run time using the LDR_CNTRL environment variable.
使用您脚本的用户不会看出其中的不同，只不过第一次调用使用内联的代码时，程序将多花一点时间来完成对嵌入代码的编译。
The user of your script will never know the difference, except that the first invocation of Inline-enabled code takes a little time to complete the compilation of the embedded code.
但是JIT编译器具有一个有限的编译时预算，而且会影响程序的运行时性能。
But JIT compilers have only a limited compile-time budget and can impact the program's run-time performance.
为了能切身体会，您可以设计一个小测试程序，这个程序当且仅当期望的条件得到满足时才可以编译。
To see this yourself, design a small test program that will compile if and only if the desired condition is true.
不同之处在于重新编译时，在这个过程中您会重用先前的预处理程序。
It's the recompilation, where you are reusing previous preprocessor passes, that will make a difference.
当应用程序向设备的主机服务器发送一个查询时，处理流程开始。 主机服务器将编译该查询并创建一个优化的查询执行计划。
The action begins when an application sends a query to the appliance host server, which compiles the query and creates an optimized query execution plan.
例如，当构建或编译一个应用程序、或执行一项磁盘密集型任务时，平均负载可能会激增。
For example, when building or compiling an application or performing a very disk intensive task, your load averages can shoot up.
样例源程序必须能在需要时被修改、编译并与软件包的剩下的部分连接起来。
The sample code must be modified as necessary, compiled, and linked with the remainder of the software package.
一般而言，菜单、工具栏和快捷键必须指向应用程序开发人员在编译时已经预期到的动作。
Generally, menus, toolbars, and shortcuts must refer to actions that the application developer has already contemplated at compile time.
当s DO的类型在编译阶段未知时，或者当程序部署完以后可能要添加新的属性时，这特别有用。
This is particularly useful when the type of the SDO is not known at compile time, or when new properties might be added after the program is deployed.
程序员每次运行构建流程并成功编译代码时，应遵循所有的应用单元测试。
Every time a programmer runs the build process and has a successful code compile, a run of all the applicable unit tests should follow.
其他应用程序当使用最新的RHEL4编译器进行重新编译时，可能也会发现性能的提高。
Other applications might also find performance gains when recompiling their applications with the latest compilers available for RHEL4.
要将其链接到可执行程序中，需要启用编译时链接器和运行时动态链接器来定位它。
To link this into executables, you need to enable both the compile-time linker and the run-time dynamic linker to find it.
使用RHEL5中的最新编辑器进行重新编译时，其他应用程序也可能获得性能改进。
Other applications might also find performance gains when recompiling with the latest compilers available for RHEL5.
如果您编译图1中的类，然后通过FxCop工具运行得到的程序集时，就会发现它会生成一个关于explicitconstructor类的严重警告。
If you compile the classes in Figure 1 and run the resulting assembly through the FxCop tool, you will find that it produces a critical warning about the ExplicitConstructor class.
如果您编译图1中的类，然后通过FxCop工具运行得到的程序集时，就会发现它会生成一个关于explicitconstructor类的严重警告。
If you compile the classes in Figure 1 and run the resulting assembly through the FxCop tool, you will find that it produces a critical warning about the ExplicitConstructor class.
应用推荐