Binary-code compatibility

Binary-code compatibility (binary compatible or <a href="/facts/Object_code/Sht3h4lW">object-code</a> compatible) is a property of a <a href="/facts/Computer_system/SQe1aK05">computer system</a>, meaning that it can run the same <a href="/facts/Executable/VSst9eLA">executable code</a>, typically <a href="/facts/Machine_code/bgdQ1Fxf">machine code</a> for a <a href="/facts/Computer/SQe1aK05">general-purpose computer</a> <a href="/facts/Central_processing_unit/Jxp1bqMV">central processing unit</a> (CPU), that another computer system can run. <a href="/facts/Source-code_compatibility/cds4bUcw">Source-code compatibility</a>, on the other hand, means that <a href="/facts/Code_compilation/WNfCDFJe">recompilation</a> or <a href="/facts/Interpreter_(computing)/JB85fbyb">interpretation</a> 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 (<a href="/facts/Instruction_set_architecture/8p8vwUeE">instruction sets</a>) of the two computers are binary compatible, but also that interfaces and behaviours of the <a href="/facts/Operating_system/8XTuvMh2">operating system</a> (OS) and <a href="/facts/Application_programming_interface/GMlN4vUr">application programming interfaces</a> (APIs), and the <a href="/facts/Application_binary_interface/wc6pmKKb">application binary interfaces</a> (ABIs) corresponding to those APIs, are sufficiently equal, i.e. "compatible".
A term like <a href="/facts/Backward_compatibility/FbHFBu5y">backward-compatible</a> 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 <a href="/facts/Application_binary_interface/wc6pmKKb">application binary interface</a> (ABI) compatibility with another system. However, it also often implies that APIs that the application depends on, directly or indirectly (such as the <a href="/facts/Windows_API/RRw4RtTu">Windows API</a>, 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 <a href="/facts/Device_driver/rDYnHU1G">device drivers</a>).
In other cases, a general <a href="/facts/Porting/7s6tFs8B">porting</a> 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 <a href="/facts/Unix/0pNL2seI">Unix</a>-based OSes, such as <a href="/facts/FreeBSD/RKsFTm7F">FreeBSD</a> or <a href="/facts/NetBSD/PTm5HWls">NetBSD</a>, offer binary compatibility with more popular OSes, such as <a href="/facts/Linux/9FvCKSTq">Linux</a>-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 <a href="/facts/Windows_3.1/zYnWyaC6">Windows 3.1</a>, <a href="/facts/Windows_95/1E1L93qC">Windows 95</a> or <a href="/facts/Windows_2000/amJIt9gz">Windows 2000</a> can also be run on <a href="/facts/Windows_XP/IozrkAYS">Windows XP</a> or <a href="/facts/Windows_7/tldLdbnX">Windows 7</a>, and many applications for <a href="/facts/DOS/sWwDXNmX">DOS</a> ran on much newer versions of Windows up to Windows 10 for as long as the <a href="/facts/NTVDM/Wv1jNzBx">NTVDM</a> was supported.

Binary-code compatibility open-in-new

Binary-code compatibility