IBMmainframe environments such as OS/360this program is known as a "linkage editor".
Unixvariants the term loader is often used as a synonym for linker. Because this usage blurs the distinction between the compile-timeprocess and the run-timeprocess, this article will use "linking" for the former and "loading" for the latter. However, in some operating systems the same program handles both the jobs of linking and loading a program; see "dynamic linking".
Computer programs are typically comprised of several parts or modules; these parts, if not all contained within a single
object file, refer to each other by means of symbols. Typically, an object file can contain three kinds of symbols:
* defined symbols, which allow it to be called by other modules,
* undefined symbols, which call the other modules where these symbols are defined, and
* local symbols, used internally within the object file to facilitate relocation.
When a program comprises multiple object files, the linker combines these files into a unified executable program, resolving the symbols as it goes along.
Linkers can take objects from a collection called a "library". Some linkers do not include the whole library in the output; they only include its symbols that are referenced from other object files or libraries. Libraries exist for diverse purposes, and one or more system libraries are usually linked in by default.
The linker also takes care of arranging the objects in a program's
address space. This may involve "relocating" code that assumes a specific base addressto another base. Since a compiler seldom knows where an object will reside, it often assumes a fixed base location (for example, zero). Relocating machine code may involve re-targeting of absolute jumps, loads and stores.
The executable output by the linker may need another relocation pass when it is finally loaded into memory (just before execution). This pass is usually omitted on hardware offering
virtual memory— every program is put into its own address space, so there is no conflict even if all programs load at the same base address.This pass may also be omitted if the executable is a position independentexecutable.
operating systemenvironments allow "dynamic linking", that is the postponing of the resolving of some undefined symbols until a program is run. That means that the executable still contains undefined symbols, plus a list of objects or libraries that will provide definitions for these. Loading the program will load these objects/libraries as well, and perform a final linking.
This approach offers two advantages:
* Often-used libraries (for example the standard system libraries) need to be stored in only one location, not duplicated in every single binary.
* If an error in a library function is corrected by replacing the library, all programs using it dynamically will benefit from the correction after restarting them. Programs that included this function by static linking would have to be re-linked first.
As the compiler has no information on the layout of objects in the final output, it cannot take advantage of shorter or more efficient instructions that place a requirement on the address of another object. For example, a jump instruction can reference an absolute address or an offset from the current location, and the offset could be expressed with different lengths depending on the distance to the target. By generating the most conservative instruction (usually the largest relative or absolute variant, depending on platform) and adding "relaxation" hints, it is possible to substitute shorter or more efficient instructions during the final link. This step can be performed only after all input objects have been read and assigned temporary addresses; the relaxation pass subsequently re-assigns addresses, which may in turn allow more relaxations to occur. In general, the substituted sequences are shorter, which allows this process to always converge on the best solution given a fixed order of objects; if this is not the case, relaxations can conflict, and the linker needs to weigh the advantages of either option.
*David William Barron, "Assemblers and Loaders". 1972, Elsevier.
*C. W. Fraser and D. R. Hanson, "A Machine Independent Linker". Software-Practice and Experience 12, 4 (April 1982).
*IBM Corporation, "Operating System 360, Linkage Editor, Program Logic Manual", 1967 [http://www.bitsavers.org/pdf/ibm/360/Y28-6610_LinkEdit(E)_PLM.pdf]
*D.W. Jones, "Assembly Language as Object Code". Software-Practice and Experience 13, 8 (August 1983)
John R. Levine: "Linkers and Loaders", Morgan-Kauffman, ISBN 1-55860-496-0
*Leon Presser, John R. White: "Linkers and Loaders". ACM Computing Surveys, Volume 4, Number 3, September 1972, pp.149-167 [http://www-inst.eecs.berkeley.edu/~cs162/sp06/hand-outs/p149-presser-linker-loader.pdf]
*Norman Ramsey, "Relocating Machine Instructions by Currying". (1996) [http://citeseer.csail.mit.edu/58313.html]
*David Salomon, "Assemblers and Loaders". 1993 [http://www.davidsalomon.name/assem.advertis/asl.pdf]
* [http://www.linuxjournal.com/article/6463 Linkers and Loaders by Sandeep Grover]
* [http://www.dpgraph.com/assembly.html Another Listing of Where to Get a Complete Collection of Free Tools for Assembly Language Development]
* [http://www.godevtool.com/ GoLink: a free linker for Windows programming]
Wikimedia Foundation. 2010.