Manidh: 1 revision imported

2023-07-26T05:31:46Z

1 revision imported

← Older revision	Revision as of 11:01, 26 July 2023
(No difference)

wikipedia>Jarble: link bounds checking using Find link

2021-07-12T21:21:57Z

link bounds checking using Find link

New page

{{More citations needed|date=December 2013}}
{{Program execution}}

In [[computer programming]], a '''runtime library''' is a set of low-level routines used by a [[compiler]] to invoke some of the behaviors of a [[runtime environment]], by inserting calls to the runtime library into compiled executable binary. The runtime environment implements the [[execution model]], built-in functions, and other fundamental behaviors of a [[programming language]].<ref name=":0" /> During execution ([[Run time (program lifecycle phase)|run time]]) of that [[computer program]], execution of those calls to the runtime library cause communication between the executable binary and the runtime environment. A runtime library often includes built-in functions for memory management or [[exception handling]].<ref name="gcc-runtime">{{cite web
| url = https://gcc.gnu.org/onlinedocs/gccint/Libgcc.html
| title = Internals of the GNU compilers, Chapter 4. The GCC low-level runtime library
| access-date = 2013-12-30
| website = gnu.org
}}</ref> Therefore, a runtime library is always specific to the platform and compiler.

The runtime library may implement a portion of the runtime environment's behavior, but if one reads the code of the calls available, they are typically only thin wrappers that simply package information, and send it to the runtime environment or operating system. However, sometimes the term ''runtime library'' is meant to include the code of the runtime environment itself, even though much of that code cannot be directly reached via a library call.

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 [[bounds checking]], 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 [[inlining]] during compilation, such as implementations of arithmetic operations not directly supported by the targeted CPU, or various miscellaneous compiler-specific operations and directives.<ref name="gcc-runtime" /><ref>{{cite web
| url = https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other-Builtins
| title = Other Built-in Functions Provided by GCC
| work = GCC Introduction
| access-date = 2013-12-30
| publisher = gnu.org
}}</ref>

The concept of a ''runtime library'' should not be confused with an ordinary [[program library]] like that created by an application programmer or delivered by a third party, nor with a [[dynamic library]], meaning a program library linked at run time. For example, the [[C programming language]] requires only a minimal runtime library (commonly called <code>[[crt0]]</code>), but defines a large standard library (called [[C standard library]]) that has to be provided by each implementation.<ref name=":0">{{cite web
| url = http://www.embecosm.com/appnotes/ean9/html/ch05s02.html
| title = The C Runtime Initialization, crt0.o
| year = 2010 | access-date = 2013-12-30
| publisher = embecosm.com
}}</ref>

== See also ==
* [[Static build]]

== References ==
{{Reflist}}

== External links ==
* [https://stackoverflow.com/questions/2766233/what-is-the-c-runtime-library What is the C runtime library?] ([[StackExchange]])

[[Category:Computer libraries]]
[[Category:Run-time systems]]

Runtime library - Revision history

Manidh: 1 revision imported

wikipedia>Jarble: link bounds checking using Find link