Runtime library

A runtime library is a <a href="/facts/Library_(computing)/xRzL3P7q">library</a> that provides access to the <a href="/facts/Runtime_environment/YmCuC4xP">runtime environment</a> that is available to a <a href="/facts/Computer_program/e38jH9N9">computer program</a> – tailored to the host <a href="/facts/Computer_platform/DmKwp5Bk">platform</a>. A runtime environment implements the <a href="/facts/Execution_model/gLPUW3Xb">execution model</a> as required for a development environment such as a particular <a href="/facts/Programming_language/cWTYbgWa">programming language</a>. A runtime library may provide basic program facilities such as for <a href="/facts/Memory_management/vthLkUpz">memory management</a> and <a href="/facts/Exception_handling/VrJxgb9r">exception handling</a>.
A runtime library is an artifact of the design of the <a href="/facts/Toolchain/SmlWCJhY">toolchain</a> used to build the program – not inherently required by the host <a href="/facts/Operating_system/8XTuvMh2">operating system</a> or the <a href="/facts/Programming_language/cWTYbgWa">programming language</a> in which the program is written. The toolset is designed to <a href="/facts/Abstraction_(computer_science)/hAnxmJle">abstract</a> aspects of the host platform – often to simplify <a href="/facts/Development_tool/wWaFqCFw">tool</a> <a href="/facts/Software_development/UUfsAaYY">development</a>. The toolchain builds a program to depend on a runtime library and to use it while the program is running – at program <a href="/facts/Run_time_(program_lifecycle_phase)/lCxKsrzB">run-time</a>. 
The runtime library may directly implement runtime behavior, but often it is a thin wrapper on top of operating system facilities. For example, some language features that can be performed only (or are more efficient or accurate) at runtime are implemented in the runtime environment and may be invoked via the runtime library API, e.g. some logic errors, array <a href="/facts/Bounds_checking/vnAjD4Lp">bounds checking</a>, dynamic type checking, exception handling, and possibly debugging functionality. For this reason, some programming bugs are not discovered until the program is tested in a "live" environment with real data, despite sophisticated compile-time checking and testing performed during development.
As another example, a runtime library may contain code of built-in low-level operations too complicated for their <a href="/facts/Inlining/jhQsJwLX">inlining</a> during compilation, such as implementations of arithmetic operations not directly supported by the targeted CPU, or various miscellaneous compiler-specific operations and directives.
The runtime library is often confused with the language <a href="/facts/Standard_library/g9QS3vy0">standard library</a> which implements functionality as defined by a language. A standard library could be implemented in a platform-specific way or it could leverage a runtime library to be platform independent. For example, the <a href="/facts/C_standard_library/qdG1nW2c">C standard library</a> is relatively large while the platform-specific runtime library (commonly called <a href="/facts/Crt0/J8D4caTP">crt0</a>) is relatively small which eases supporting multiple platforms.

Runtime library open-in-new

Runtime library