binary-code compatibility

Uses your system voice; voice and rate in settings.

Q13912071Snapshot

≈ 4 min read

Names in other languages

  • Englishbinary-code compatibility
  • EnglishBinary code compatibility
  • EnglishBinary code compatibility
  • РусскийДвоичная совместимость
  • DeutschBinärkompatibilität
  • 日本語バイナリコードの互換性
  • 繁體中文二進位制程式碼相容性
  • 中文二進制代碼相容性

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Binary-code compatibility (binary compatible or object-code compatible) is a property of a computer system, meaning that it can run the same executable code, typically machine code for a general-purpose computer central processing unit (CPU), that another computer system can run. Source-code compatibility, on the other hand, means that recompilation or interpretation is necessary before the program can be run on the compatible system.

For a compiled program on a general operating system, binary compatibility often implies that not only the CPUs (instruction sets) of the two computers are binary compatible, but also that interfaces and behaviours of the operating system (OS) and application programming interfaces (APIs), and the application binary interfaces (ABIs) corresponding to those APIs, are sufficiently equal, i.e. "compatible". A term like backward-compatible usually implies object-code compatibility.

This means that newer computer hardware and/or software has (practically) every feature of the old, plus additional capabilities or performance. Older executable code will thus run unchanged on the newer product.

For a compiled program running directly on a CPU under an OS, a "binary compatible operating system" primarily means application binary interface (ABI) compatibility with another system.…

Binary-code compatibility (binary compatible or object-code compatible) is a property of a computer system, meaning that it can run the same executable code, typically machine code for a general-purpose computer central processing unit (CPU), that another computer system can run. Source-code compatibility, on the other hand, means that recompilation or interpretation is necessary before the program can be run on the compatible system.

For a compiled program on a general operating system, binary compatibility often implies that not only the CPUs (instruction sets) of the two computers are binary compatible, but also that interfaces and behaviours of the operating system (OS) and application programming interfaces (APIs), and the application binary interfaces (ABIs) corresponding to those APIs, are sufficiently equal, i.e. "compatible". A term like backward-compatible usually implies object-code compatibility.

This means that newer computer hardware and/or software has (practically) every feature of the old, plus additional capabilities or performance. Older executable code will thus run unchanged on the newer product.

For a compiled program running directly on a CPU under an OS, a "binary compatible operating system" primarily means application binary interface (ABI) compatibility with another system. However, it also often implies that APIs that the application depends on, directly or indirectly (such as the Windows API, for example), are sufficiently similar.

Hardware (besides the CPU, such as for graphics) and peripherals that an application accesses may also be a factor for full compatibility, although many hardware differences are hidden by modern APIs (often partly supplied by the OS itself and partly by specific device drivers). In other cases, a general porting of the software must be used to make non-binary-compatible programs work.

Binary compatibility is a major benefit when developing computer programs that are to be run on multiple OSes. Several Unix-based OSes, such as FreeBSD or NetBSD, offer binary compatibility with more popular OSes, such as Linux-derived ones, since most binary executables are not commonly distributed for such OSes.

Most OSes provide binary compatibility, in each version of the OS, for most binaries built to run on earlier versions of the OS. For example, many executables compiled for Windows 3.1, Windows 95 or Windows 2000 can also be run on Windows XP or Windows 7, and many applications for DOS ran on much newer versions of Windows up to Windows 10 for as long as the NTVDM was supported.

See also

Backward compatibility Application binary interface (ABI) Computer compatibility Bug compatibility Plug compatibility Video game remake Multi-architecture binary

KDE Techbase Policies – a compendium of C++ development rules of thumb (with some examples) for not breaking binary compatibility between releases of a library. ABI Analysis Tools a set of open-source tools for analysis of ABI and backward binary compatibility implementing KDE Techbase Policies de:Kompatibilität (Technik)#Binärkompatibilität

Text derived from https://en.wikipedia.org/w/index.php?oldid=1373496845 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot binary-code-compatibility-1507758-60212e9f4ca102ea · hash 60212e9f4ca102ea636546a7702cfddd0e220e0f561e0f1bca5449551c99b7a0 · captured 1788674839.0 · version history

Cite this page as: encyclopegia.org, “binary-code compatibility”, snapshot binary-code-compatibility-1507758-60212e9f4ca102ea. https://encyclopegia.org/a/binary-code-compatibility

Sources cited in this revision

No external citation was extracted for this revision. That is a statement about the source, not a claim that none exists.