GNU ld

GNU ld
Qef · Public domain · source
Name	GNU ld
Developer	GNU Project
Released	1980s
Operating system	Unix-like, Windows (via ports)
License	GNU General Public License

GNU ld

Overview

GNU ld is the linker distributed by the GNU Project as part of the GNU Binutils collection. It resolves symbol references, combines object files, and produces executable and library artifacts for targets such as Linux, FreeBSD, NetBSD, OpenBSD, and Microsoft Windows. As a component used in toolchains alongside GCC, Clang, and LLVM, it plays a central role in building software for projects including the Linux kernel, GNU C Library, and many BSD-derived systems. Implementations and ports have made it relevant to cross-compilation efforts for ARM, MIPS, PowerPC, and x86 ecosystems.

History and Development

Development of ld traces to the early days of the GNU Project and the need to replace proprietary linkers used on Unix systems; contributions and maintenance have come from engineers affiliated with organizations such as the Free Software Foundation, academic institutions, and corporate partners. Over decades, ld evolved alongside toolchain shifts driven by the rise of POSIX-compatible systems, the emergence of ELF as a dominant binary format, and the adoption of new optimization and security practices influenced by projects like PaX and SELinux. Major enhancements often coordinated with releases of GCC and Binutils and have been discussed at developer venues including GNU conferences and Linux kernel mailing list threads. Porting work has been informed by standards bodies such as ISO for C language linkage conventions and by hardware vendors including Intel, ARM Holdings, and IBM.

Features and Functionality

GNU ld implements symbol resolution, relocation processing, and layout of sections and segments according to target object formats such as ELF, COFF, and PE. It supports creation of static executables, shared libraries, position-independent executables used by projects like OpenSSH, and linker scripts enabling custom memory maps used in embedded systems for vendors such as STMicroelectronics and NXP Semiconductors. The linker can perform garbage collection of unused sections (GC-sections), handle symbol versioning employed by glibc and other runtime libraries, and emit linker-generated symbols useful to runtime systems like glibc and musl. Security-related features include support for RELRO and symbol visibility controls leveraged by maintainers of Chromium and Firefox.

Command-Line Interface and Options

The ld executable exposes a long-standing command-line interface with options such as --oformat, --script, --shared, --static, --soname, and --Map to control output format, linker scripts, shared object semantics, static linking, shared object naming conventions, and map file generation. Common invocations are coordinated by build systems like GNU Make, Autoconf, CMake, and package managers such as Debian and RPM-based distributions. Linker scripts use directives to define MEMORY regions and SECTIONS for specialized projects including U-Boot and FreeRTOS ports. The toolchain integration often occurs via driver programs like gcc and wrappers in build environments of projects such as OpenSSL and LibreOffice.

Supported Formats and Platforms

GNU ld supports ELF for Unix-like targets, COFF/PE for Windows-targeted toolchains, and historical and niche formats used by embedded toolchains. Platform support spans architectures including x86-64, i386, ARM, AArch64, MIPS64, PowerPC64, and mainframes from IBM System z. Cross-linking targets are enabled by multi-target binutils builds used by distributors such as Debian GNU/Linux, Fedora Project, and Gentoo Linux. Community ports and adaptations have allowed use with embedded real-time operating systems like VxWorks and with bootloaders such as GRUB.

Internals and Implementation

Internally, ld is implemented in the C programming language and organized into subsystems for symbol tables, relocation processing, and section merging; its codebase is maintained within the GNU Savannah and mirrored in many repositories used by distributions. The linker handles relocation types defined by architecture-specific ABIs, consults symbol resolution rules specified by standards such as System V ABI, and uses data structures optimized for large applications such as kernel and large-scale server software like Apache HTTP Server. Performance and correctness patches have originated from corporate contributors including engineers from Red Hat, Intel Corporation, and embedded vendors; debugging and testing workflows integrate with continuous integration systems used by projects like GitLab and GitHub.

Usage Examples and Integration

Typical use involves invoking the tool through compile-driver programs like GCC or Clang which pass object files and libraries to ld; for example, linking static binaries for utilities in distributions like BusyBox or shared libraries for database systems such as PostgreSQL. Advanced usage leverages linker scripts for custom memory layout in embedded firmware projects maintained by vendors like STMicroelectronics or toolchains for Raspberry Pi development. Integration into build systems follows patterns used by Makefile-based projects, Autotools-driven packages, and CMake-orchestrated builds; packaging and distribution in ecosystems like Debian or Fedora Project require precise control over sonames and symbol versions handled by ld.

Category:Linkers