Link time: Difference between revisions
Content added Content deleted
(Created) |
m (Moved to Life cycle cat, link) |
||
| Line 1: | Line 1: | ||
| ⚫ | [[Category:Program life cycle]]'''Link time''' refers to the linking phase of the program life cycle. Link-time actions are performed by the [[OS]] linker and/or loader. The main objective of linking is mapping the higher-level language semantics onto the lower-level environment ([[OS]] and the hardware). Traditionally this includes address translation, binding the external objects (modules), code optimization, machine code translation (like for example in [[OpenVMS]]). |
||
[[Category:Encyclopedia]] |
|||
| ⚫ | |||
| ⚫ | '''Link time''' refers to the linking phase of the program life cycle. Link-time actions are performed by the [[OS]] linker and/or loader. The main objective of linking is mapping the higher-level language semantics onto the lower-level environment ([[OS]] and the hardware). Traditionally this includes address translation, binding the external objects (modules), code optimization, machine code translation (like for example in [[OpenVMS]]). |
||
| ⚫ | |||
Latest revision as of 15:27, 26 August 2008
Link time refers to the linking phase of the program life cycle. Link-time actions are performed by the OS linker and/or loader. The main objective of linking is mapping the higher-level language semantics onto the lower-level environment (OS and the hardware). Traditionally this includes address translation, binding the external objects (modules), code optimization, machine code translation (like for example in OpenVMS).
The linker's input is the object code generated by the compiler. The output is either an executable code or a partially linked code in the form of an object library or a dynamically linked library.