通常，大部分非线程的应用程序在SLES8和SLES9 中是二进制兼容的。
In general, most nonthreaded applications will be binary compatible between SLES8 and SLES9.
ReactOS是一种开源的windows二进制兼容的操作系统，允许执行多个Windows应用程序。
ReactOS is an open source Windows binary-compatible operating system that permits the execution of many Windows applications.
由于RHEL 3和SLES8所提供的线程模型不同，所以当然不能认为会有完全的二进制兼容性。
Due to the differences in threading models offered by RHEL3 and SLES8, complete binary compatibility cannot be taken for granted.
当尝试获得二进制兼容性时，核心程序库的重要变化也会引发问题。
Major changes in core libraries can also present a problem when trying to achieve binary compatibility.
POWER 5处理器包含了对POWER 4架构的改进，同时保持了两者间的二进制兼容性，这就使得您可以在这两个平台上运行相同的应用程序。
The POWER5 architecture contains enhancements to the POWER4 architecture while maintaining binary compatibility between the two, which allows you to run the same application on both platforms.
自1995年以来，64-位处理器实现了完整的体系结构，支持与现有32 -位应用程序的完全二进制应用程序兼容，并完全支持新的64 -位应用程序。
Since 1995, 64-bit processors have implemented the complete architecture, allowing full binary application compatibility with existing 32-bit applications and support for new 64-bit applications.
虽然这些优化在它们各自的架构上提高了性能，但是可能会影响运行在其他平台上的应用程序的二进制兼容性。
While these optimizations improve performance on their respective architectures, they may compromise binary compatibility for applications running on other platforms.
API工具——api工具提供了一个构造器(builder)，可以报告工作区(workspace)中的API使用和二进制兼容性错误。
API tooling - API tooling provides a builder that reports API usage and binary compatibility errors in the workspace.
在本地32-位PowerPC环境以及64 -位POWER环境中运行的32 -位应用程序之间存在二进制兼容性。
Binary compatibility between 32-bit applications running in native 32-bit PowerPC environments and 64-bit POWER environments exists.
不过，为了确保二进制兼容性，RedHat建议您将您的应用程序接口链接到它们所定义的核心库。
However, to ensure binary compatibility, Red hat recommends that you link your application interfaces to the core libraries they have defined. This list includes.
例如，在SLES8系统中使用glibc版本2.2.5编译的二进制代码，将可以在SLES9系统中使用glibc版本2.3运行，因为2.3版本是向后兼容的。
For example, a binary that was compiled on a SLES8 system with a version of glibc at 2.2.5 will also run on a SLES9 system with a glibc version at 2.3 since the 2.3 version is backward compatible.
二进制兼容性是指能够在特定处理器系列的多个环境中运行二进制文件的能力。
Binary compatibility is the ability to take a binary and run it on multiple environments of a given processor family.
通过了解二进制兼容性所涉及的问题，可以达成这些目标。
These goals can be achieved by understanding the issues that are involved with binary compatibility.
“二进制兼容性概述”中的最后一个示例涉及到了在不同的处理器类型中运行二进制代码——POWER 4处理器和POWER 5处理器。
The last example under "Overview of binary compatibility" involved running a binary on two different processor types — a POWER4 processor and a POWER5 processor.
但是以你对目前的映射的理解，你一定会注意到将来的版本中任何可能的二进制不兼容性。
Your understanding of the present mapping will ensure that you are alerted to any possible binary incompatibilities with future versions.
POWER5体系结构是对POWER4 体系结构的改进，但是保持了二进制与结构的兼容性。
The POWER5 architecture is an enhancement of the POWER4 architecture, but maintains binary and structural compatibility.
记住，重新编译以获得性能改进可能会损害二进制文件在某些环境中的兼容性。
Keep in mind that recompiling to gain performance enhancements may compromise binary compatibility on some environments.
另外，AIX7与在以前的AIX版本上开发的应用程序保持完全的二进制兼容，只要这些程序符合合理的编程标准即可。
Additionally, AIX 7 will have full binary compatibility for application programs developed on prior versions of aix-as long as these programs comply with reasonable programming standards.
重要的是要紧记：通过重新编译来获得性能提升可能会影响某些环境中的二进制兼容性。
It is important to keep in mind that recompiling to gain performance enhancements may compromise binary compatibility on some environments.
“二进制兼容性概述”小节讨论的最后一个例子涉及到在两个不同的处理器类型上运行相同的二进制文件：POWER 5处理器和POWER 6处理器。
The last example under "Overview of binary compatibility" involved running a binary on two different processor types: a POWER5 processor and a POWER6 processor.
关于与其他选项的兼容性和与GCC 3.0以前的版本生成的二进制代码的调用兼容性，请参考GCC手册获得详细情况。
Refer to the GCC manual for details concerning the compatibility with other options and for call-compatibility with binary code generated by pre-3.0 versions of GCC.
我们还需要清楚地了解gtk +中的应用程序二进制接口(abi)兼容性到底意味着什么。
You also need to know exactly what application binary interface (ABI) -compatibility means in GTK +.
在SOAP请求中嵌入二进制信息的通常做法是对信息进行BASE64编码，使它能兼容xml。
A common means of embedding binary information in a SOAP request is to apply BASE64 encoding to the information, rendering it XML compatible.
这不是AIX二进制兼容性语句的破坏，而是不支持32 位内核扩展。
This is not a breakage of the AIX binary compatibility statement, but a fact that 32-bit kernel extensions are not supported.
您可以使用图1所示的流程图来确定某个应用程序在RHEL orSLES中是否具备二进制兼容性。
You can use the flowchart in Figure 1 to determine if an application is binary compatible on RHEL or SLES.
为了避免这种情况，可以在AspectJ中声明其他类型的成员或者父类，包括接口的默认实现，只要所有定义保持二进制兼容即可。
To avoid that, in AspectJ you can declare members and parents of other types, including default implementations for interfaces, as long as any definition preserves binary compatibility.
这种处理器是Power 4处理器的单核心(single - core)版本，它保持了与Power架构家族其他成员的二进制兼容性。
This processor is a single-core version of the POWER4 processor, which maintains binary compatibility with other members of the Power Architecture family.
在GCC4.0的发布版中，我们对gcj实现了一种新的编译方式，称之为二进制兼容性abi (Binary Compatibility Application Binary Interface)。
For the GCC 4.0 release we implemented a new compilation mode for GCJ, called the Binary Compatibility ABI.
更关键的因素似乎在于10多年来Microsoft一直在坚定不移地保持着与遗留Microsoftoffice二进制格式的完美兼容性。
The critical factor seems to be that Microsoft is dead-set on maintaining pixel-perfect compatibility with at least 10 years of legacy Microsoft Office binary formats.
尽管上面列出的这些包是专门为OpenBSD 进行移植的，但该平台的另一条原则是二进制兼容性。
While the packages listed above have been specifically ported for OpenBSD, another tenet of the platform is binary compatibility.
应用推荐