a.out

a.out

a.out was the original executable and object file format used in early Unix systems, developed at Bell Labs by researchers including Ken Thompson and Dennis Ritchie. It served as the default binary format for toolchains on numerous historical platforms such as PDP-11, VAX, Sun workstations, and early BSD releases, and influenced the design of later formats like ELF and COFF. The format’s simple header and segment layout made it suitable for early linkers and loaders in environments from academic University of California, Berkeley research to commercial systems from AT&T and UNIX System Laboratories.

History

The format originated during the late 1960s and early 1970s in the development of Unix at Bell Labs, tying into seminal work by Ken Thompson and Dennis Ritchie on operating system and language design. Early adopters included machines from Digital Equipment Corporation such as the PDP-11 and later the VAX family developed by DEC. As Unix spread to academic institutions including University of California, Berkeley and commercial vendors like Sun Microsystems, the format became ubiquitous across variants including 4.2BSD and System V. During the 1980s and 1990s, competing executable formats such as COFF (originating at AT&T and UNIX System Laboratories) and later ELF (driven by projects like System V Release 4 and adopted by Linux and Solaris) led to gradual migration away from the original format. Various standardization efforts and platform transitions—such as those driven by POSIX committees and processor architecture shifts to x86-64—accelerated adoption of successor formats.

File format and structure

The format is identified by a compact fixed-size header placed at the start of the file, containing fields for magic numbers, segment sizes, and entry point addresses. Implementations on architectures like PDP-11, VAX, MIPS, and SPARC adapted header semantics to match architecture-specific alignment and relocation models. Typical header fields include code size, data size, uninitialized data (BSS) size, symbol table offset, and relocation table size; these are analogous to fields later formalized in COFF and ELF. The format separates text (code) and data segments, with the BSS segment represented implicitly by a size field rather than stored bytes. Symbol table and relocation records are appended after segment bytes, containing symbol entries for linkers produced by assemblers and compilers such as those developed at Bell Labs and by vendors like GCC contributors associated with Free Software Foundation.

Execution and linking

Execution semantics for the format were simple: the kernel’s loader read the header, allocated memory for text, data, and BSS, performed relocations specified by relocation entries, and transferred control to the entry point. Linking tools—linkers and loaders written for toolchains including ld variants—resolved external references using symbol tables produced by assemblers and compilers, such as those from GCC, Portable C Compiler maintainers, and vendor toolchains like Sun Studio. Dynamic linking was not part of the original design; later extensions and platform-specific patches introduced shared library mechanisms and position-independent code practices popularized by Linux and FreeBSD developers. The limitations of relocation scalability and lack of uniform dynamic linking metadata motivated migration to formats offering richer runtime linking support, such as ELF with its dynamic segment and dynamic symbol table.

Implementations and platform variations

Numerous Unix derivatives implemented variations of the format to match architecture constraints. BSD variants on PDP-11 and VAX used slightly different header conventions than System V ports on Sun Microsystems SPARC and IBM POWER systems. Academic implementations at University of California, Berkeley produced toolchains and kernels that handled symbol and relocation layouts tuned for their campus clusters and research machines. Third-party vendors such as DEC and Sun Microsystems adapted assemblers and linkers for native compilers including vendor-specific optimizations. Open-source ecosystems—NetBSD, OpenBSD, and FreeBSD—historically included compatibility layers and utilities to read or convert legacy binaries. Cross-compilation environments and early embedded toolchains also produced a.out variants for architectures like Motorola 68000 and early ARM designs, reflecting bespoke relocation and alignment needs.

Migration and legacy impact

The rise of more expressive formats such as ELF and COFF during the 1990s precipitated migrations by major systems including Linux, Solaris, and System V Release 4. These successor formats provided standardized dynamic linking, symbol versioning, and richer metadata for debuggers like GDB and profiling tools such as gprof. Despite deprecation, a.out’s simple design influenced educational materials and historical studies at institutions like MIT and Carnegie Mellon University, and its legacy persists in utilities and emulators that parse legacy binaries. Compatibility work by projects including Binutils and platform maintainers ensured transitional support, while archival interest by computing historians and museums—such as Computer History Museum—keeps documentation alive. The architectural lessons from the format informed modern executable standards used by contemporary operating systems from Microsoft to Apple and open-source communities represented by GNU Project and Debian.

Category:Executable file formats