使用调试编译器。
Other compilers may name things differently.
其他编译器可能有不同的命名方式。
All XLC and XLF compilers need to be installed.
必需安装所有的XLC和XLF编译器。
Not all JIT compilers generate the code as above.
不是所有的JIT编译器都生成如上代码。
Supporting both compilers is vital for developer productivity.
同时支持两个编译器，对于提高开发人员的生产效率是至关重要的。
You need to make sure to install all the XLC and XLF compilers.
需要确保安装所有的XLC和XLF编译器。
The parsers behave more like interpreters and are not compilers.
解析器的行为更像解释器，而不是编译器。
Development environment (compilers, make utilities, and so on).
开发环境(编译器，make工具，等等)。
Two heavily optimized Just-In-Time compilers (-client and -server).
两个重度优化的即时编译器(- client和- server)。
But keep in mind, too, that different compilers adopt different models.
但是，也不要忘记，不同的编译器采用的是不同的对象模型。
It is not possible to compile code by hand, so they always use compilers.
手工编译代码绝无可能，所以他们一定要用到编译器。
Current projects seem to meet their needs just by tuning their Fortran compilers.
只要通过调优他们的Fortran编译器，当前的项目似乎就满足了他们的需求。
Not all compilers are flexible enough or provide these types of services, however.
但并不是所有编译器都足够灵活到可以提供这些服务。
The only problem is that right now very few compilers implement tail-call optimizations.
惟一的问题在于，现在只有非常少的编译器实现了尾部调用优化。
This pseudo code is not only possible, but is exactly what happens on some JIT compilers.
这段伪代码不仅是可能的，而且是一些JIT编译器上真实发生的。
Listing 5 shows the code that proves the point on compilers optimizing empty base classes.
清单5给出的代码在优化了空基类的编译器上证明了这一点。
Supported C compilers: See the Resources section, subsection "Get products and technologies."
受支持的C编译器：见参考资料小节中的 “获得产品和技术” 小节。
Neither Eclipse nor GDB understand the debugging information generated by Microsoft compilers.
Eclipse或 GDB都不能理解由Microsoft 编译器生成的调试信息。
These gains come about because of different libraries, processor features, and updated compilers.
这些提高来自于不同的程序库、处理器特性以及得到更新的编译器。
The compilers are highly tunable, with a large number of options for tweaking the generated code.
编译器是高度可调优的，有大量调整生成代码的选项。
Cross compilers are available for 32-bit PowerPC Linux systems and 64-bit Linux on POWER systems.
还存在可以同时在32位PowerPCLinux系统和64位LinuxonPOWER系统上运行的跨系统编译器。
In fact, most modern JIT compilers also support recompiling methods that are found to be very hot.
事实上，大部分现代的JIT编译器也支持重编译被认为是热方法的方法。
Many compilers can generate more efficient code for this by putting the tables in read-only memory.
很多编译器通过将表放入只读内存中可以生成更高效的代码。
It is a software optimization and analysis framework that can be used by other compilers and tools.
Phoenix不仅仅限于一个编译器，它还是一个软件优化和分析框架，能被其他编译器和工具使用。
Even though these two compilers produce similar output, their implementation is completely different.
尽管这两个编译器产生类似的输出，但是他们的实现却完全不同。
Certainly with the availability of such cross-platform compilers as MinGW or Cygwin, this could be easy.
当然，随着MinGW或Cygwin等跨平台编译器的可用，这可能会很容易。
For example, the noinline, noreturn, deprecated, and naked attributes enjoy support from both compilers.
例如，这两种编译器都支持noinline、noreturn、deprecated和naked属性。
For example, the noinline, noreturn, deprecated, and naked attributes enjoy support from both compilers.
例如，这两种编译器都支持noinline、noreturn、deprecated和naked属性。
应用推荐