CACrown ArchivesHistory · sources · collections
Menu
Research dossier · Science & Nature

Relocation (computing)

in computing, the process of assigning load addresses for position-dependent code and data

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 21, 2026
Entity authorityQ3499564
Source-derived summary

In software development, relocation is the process of assigning load addresses for position-dependent code and data of a program and adjusting the code and data to reflect the assigned addresses.

A linker usually performs relocation in conjunction with symbol resolution, the process of searching files and libraries to replace symbolic references or names of libraries with actual usable addresses in memory before running a program.

Relocation is typically done by the linker at link time, but it can also be done at load time by a relocating loader, or at run time by the running program itself.

Segmentation

Object files are typically segmented into various memory segments or section types. Example segment types include code segment (.text), initialized data segment (.data), uninitialized data segment (.bss), or others as established by the programmer, such as common segments or named static segments.

Relocation table

The relocation table is a list of addresses created by a compiler or assembler and stored in the object or executable file. Each entry in the table references an absolute address in the object code that must be changed when the loader relocates the program so that it will refer to the correct location. Entries in the relocation table are known as fixups and are designed to support relocation of the program as a complete unit. In some cases, each fixup in the table is itself relative to a base address of zero, so the fixups themselves must be changed as the loader moves through the table.

In some architectures, a fixup that crosses certain boundaries (such as a segment boundary) or that is not aligned on a word boundary is illegal and flagged as an error by the linker.

Editorial summary

“Relocation (computing)” enters the record as in computing, the process of assigning load addresses for position-dependent code and data. Crown Archives preserves that source wording while asking what Relocation, computing and process can confirm, complicate or overturn.

Editorial reviewA practical orientation to terminology and classification, particularly when read beside dated observations, specimens or technical literature. The current 282-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. Its strongest next move is a source search built around Relocation, computing and process.
Editorial analysis

Why this record matters

“Relocation (computing)” is worth following because a concise public description often conceals a longer documentary argument. Here, Relocation, computing and process provides the most credible route into that argument.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Aug 21, 2026. The linked authority identifier is Q3499564. None of the 0 selected statements returned an explicit reference.

Critical limits

Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “Relocation (computing)”, its source revision and the description used here.
  2. Expand the search: follow Relocation (computing) primary sources, Relocation (computing) archive and Relocation research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Relocation (computing)”?
  2. Which observation, specimen, dataset or publication supports the account?
  3. Has classification or technical consensus changed since the cited source?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Relocation (computing)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.