Linux Standard Base Core Specification for PPC32 3.2

Copyright © 2007 Linux Foundation

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

Portions of the text may be copyrighted by the following parties:

  • The Regents of the University of California

  • Free Software Foundation

  • Ian F. Darwin

  • Paul Vixie

  • BSDI (now Wind River)

  • Andrew G Morgan

  • Jean-loup Gailly and Mark Adler

  • Massachusetts Institute of Technology

  • Apple Inc.

  • Easy Software Products

  • artofcode LLC

  • Till Kamppeter

  • Manfred Wassman

  • Python Software Foundation

These excerpts are being used in accordance with their respective licenses.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

UNIX is a registered trademark of The Open Group.

LSB is a trademark of the Linux Foundation in the United States and other countries.

AMD is a trademark of Advanced Micro Devices, Inc.

Intel and Itanium are registered trademarks and Intel386 is a trademark of Intel Corporation.

PowerPC is a registered trademark and PowerPC Architecture is a trademark of the IBM Corporation.

S/390 is a registered trademark of the IBM Corporation.

OpenGL is a registered trademark of Silicon Graphics, Inc.

Table of Contents
Foreword
Introduction
I. Introductory Elements
1. Scope
1.1. General
1.2. Module Specific Scope
2. References
2.1. Normative References
2.2. Informative References/Bibliography
3. Requirements
3.1. Relevant Libraries
3.2. LSB Implementation Conformance
3.3. LSB Application Conformance
4. Definitions
5. Terminology
6. Documentation Conventions
II. Executable And Linking Format (ELF)
7. Introduction
8. Low Level System Information
8.1. Machine Interface
8.2. Function Calling Sequence
8.3. Operating System Interface
8.4. Process Initialization
8.5. Coding Examples
8.6. C Stack Frame
8.7. Debug Information
9. Object Format
9.1. Introduction
9.2. ELF Header
9.3. Sections
9.4. Symbol Table
9.5. Relocation
10. Program Loading and Dynamic Linking
10.1. Introduction
10.2. Program Header
10.3. Program Loading
10.4. Dynamic Linking
III. Base Libraries
11. Libraries
11.1. Program Interpreter/Dynamic Linker
11.2. Interfaces for libc
11.3. Data Definitions for libc
11.4. Interfaces for libm
11.5. Data Definitions for libm
11.6. Interfaces for libpthread
11.7. Data Definitions for libpthread
11.8. Interfaces for libgcc_s
11.9. Data Definitions for libgcc_s
11.10. Interface Definitions for libgcc_s
11.11. Interfaces for libdl
11.12. Data Definitions for libdl
11.13. Interfaces for libcrypt
IV. Utility Libraries
12. Libraries
12.1. Interfaces for libz
12.2. Data Definitions for libz
12.3. Interfaces for libncurses
12.4. Data Definitions for libncurses
12.5. Interfaces for libutil
V. Package Format and Installation
13. Software Installation
13.1. Package Dependencies
13.2. Package Architecture Considerations
A. Alphabetical Listing of Interfaces
A.1. libc
A.2. libcrypt
A.3. libdl
A.4. libgcc_s
A.5. libm
A.6. libpthread
A.7. librt
A.8. libutil
B. GNU Free Documentation License (Informative)
B.1. PREAMBLE
B.2. APPLICABILITY AND DEFINITIONS
B.3. VERBATIM COPYING
B.4. COPYING IN QUANTITY
B.5. MODIFICATIONS
B.6. COMBINING DOCUMENTS
B.7. COLLECTIONS OF DOCUMENTS
B.8. AGGREGATION WITH INDEPENDENT WORKS
B.9. TRANSLATION
B.10. TERMINATION
B.11. FUTURE REVISIONS OF THIS LICENSE
B.12. How to use this License for your documents
List of Figures
8-1. Initial Process Stack
List of Tables
2-1. Normative References
2-2. Other References
3-1. Standard Library Names
8-1. Scalar Types
8-2. Extra Auxiliary Types
9-1. ELF Special Sections
9-2. Additional Special Sections
11-1. libc Definition
11-2. libc - RPC Function Interfaces
11-3. libc - System Calls Function Interfaces
11-4. libc - System Calls Deprecated Function Interfaces
11-5. libc - Standard I/O Function Interfaces
11-6. libc - Standard I/O Data Interfaces
11-7. libc - Signal Handling Function Interfaces
11-8. libc - Signal Handling Deprecated Function Interfaces
11-9. libc - Signal Handling Data Interfaces
11-10. libc - Localization Functions Function Interfaces
11-11. libc - Localization Functions Data Interfaces
11-12. libc - Posix Spawn Option Function Interfaces
11-13. libc - Posix Advisory Option Function Interfaces
11-14. libc - Socket Interface Function Interfaces
11-15. libc - Socket Interface Data Interfaces
11-16. libc - Wide Characters Function Interfaces
11-17. libc - String Functions Function Interfaces
11-18. libc - String Functions Deprecated Function Interfaces
11-19. libc - IPC Functions Function Interfaces
11-20. libc - Regular Expressions Function Interfaces
11-21. libc - Character Type Functions Function Interfaces
11-22. libc - Time Manipulation Function Interfaces
11-23. libc - Time Manipulation Data Interfaces
11-24. libc - Terminal Interface Functions Function Interfaces
11-25. libc - System Database Interface Function Interfaces
11-26. libc - System Database Interface Deprecated Function Interfaces
11-27. libc - Language Support Function Interfaces
11-28. libc - Large File Support Function Interfaces
11-29. libc - Large File Support Deprecated Function Interfaces
11-30. libc - Standard Library Function Interfaces
11-31. libc - Standard Library Deprecated Function Interfaces
11-32. libc - Standard Library Data Interfaces
11-33. libm Definition
11-34. libm - Math Function Interfaces
11-35. libm - Math Deprecated Function Interfaces
11-36. libm - Math Data Interfaces
11-37. libpthread Definition
11-38. libpthread - Realtime Threads Function Interfaces
11-39. libpthread - Advanced Realtime Threads Function Interfaces
11-40. libpthread - Posix Threads Function Interfaces
11-41. libpthread - Posix Threads Deprecated Function Interfaces
11-42. libpthread - Thread aware versions of libc interfaces Function Interfaces
11-43. libgcc_s Definition
11-44. libgcc_s - Unwind Library Function Interfaces
11-45. libdl Definition
11-46. libdl - Dynamic Loader Function Interfaces
11-47. libcrypt Definition
11-48. libcrypt - Encryption Function Interfaces
12-1. libz Definition
12-2. libncurses Definition
12-3. libutil Definition
12-4. libutil - Utility Functions Function Interfaces
A-1. libc Function Interfaces
A-2. libc Data Interfaces
A-3. libcrypt Function Interfaces
A-4. libdl Function Interfaces
A-5. libgcc_s Function Interfaces
A-6. libm Function Interfaces
A-7. libm Data Interfaces
A-8. libpthread Function Interfaces
A-9. librt Function Interfaces
A-10. libutil Function Interfaces

Foreword

This is version 3.2 of the Linux Standard Base Core Specification for PPC32. This specification is part of a family of specifications under the general title "Linux Standard Base". Developers of applications or implementations interested in using the LSB trademark should see the Linux Foundation Certification Policy for details.

Introduction

The LSB defines a binary interface for application programs that are compiled and packaged for LSB-conforming implementations on many different hardware architectures. Since a binary specification shall include information specific to the computer processor architecture for which it is intended, it is not possible for a single document to specify the interface for all possible LSB-conforming implementations. Therefore, the LSB is a family of specifications, rather than a single one.

This document should be used in conjunction with the documents it references. This document enumerates the system components it includes, but descriptions of those components may be included entirely or partly in this document, partly in other documents, or entirely in other reference documents. For example, the section that describes system service routines includes a list of the system routines supported in this interface, formal declarations of the data structures they use that are visible to applications, and a pointer to the underlying referenced specification for information about the syntax and semantics of each call. Only those routines not described in standards referenced by this document, or extensions to those standards, are described in the detail. Information referenced in this way is as much a part of this document as is the information explicitly included here.

The specification carries a version number of either the form x.y or x.y.z. This version number carries the following meaning:

Since this specification is a descriptive Application Binary Interface, and not a source level API specification, it is not possible to make a guarantee of 100% backward compatibility between major releases. However, it is the intent that those parts of the binary interface that are visible in the source level API will remain backward compatible from version to version, except where a feature marked as "Deprecated" in one release may be removed from a future release.

Implementors are strongly encouraged to make use of symbol versioning to permit simultaneous support of applications conforming to different releases of this specification.

I. Introductory Elements

Table of Contents
1. Scope
1.1. General
1.2. Module Specific Scope
2. References
2.1. Normative References
2.2. Informative References/Bibliography
3. Requirements
3.1. Relevant Libraries
3.2. LSB Implementation Conformance
3.3. LSB Application Conformance
4. Definitions
5. Terminology
6. Documentation Conventions

Chapter 1. Scope

1.1. General

The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360 Part 1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

ISO/IEC 23360 Part 1, the LSB-generic document, should be used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

1.2. Module Specific Scope

This is the PPC32 architecture specific Core part of the Linux Standard Base (LSB). This part supplements the generic LSB Core module with those interfaces that differ between architectures.

Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Chapter 2. References

2.1. Normative References

The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

Note: Where copies of a document are available on the World Wide Web, a Uniform Resource Locator (URL) is given for informative purposes only. This may point to a more recent copy of the referenced specification, or may be out of date. Reference copies of specifications at the revision level indicated may be found at the Linux Foundation's Reference Specifications site.

Table 2-1. Normative References

NameTitleURL
ISO/IEC 23360 Part 1ISO/IEC 23360:2005 Linux Standard Base - Part 1 Generic Specificationhttp://www.linuxbase.org/spec/
Filesystem Hierarchy StandardFilesystem Hierarchy Standard (FHS) 2.3http://www.pathname.com/fhs/
ISO C (1999)ISO/IEC 9899: 1999, Programming Languages --C
ISO POSIX (2003)

ISO/IEC 9945-1:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 1: Base Definitions

ISO/IEC 9945-2:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 2: System Interfaces

ISO/IEC 9945-3:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 3: Shell and Utilities

ISO/IEC 9945-4:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 4: Rationale

Including Technical Cor. 1: 2004

http://www.unix.org/version3/
Large File SupportLarge File Supporthttp://www.UNIX-systems.org/version2/whatsnew/lfs20mar.html
SUSv2CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606)http://www.opengroup.org/publications/catalog/un.htm
SVID Issue 3American Telephone and Telegraph Company, System V Interface Definition, Issue 3; Morristown, NJ, UNIX Press, 1989. (ISBN 0201566524)
SVID Issue 4System V Interface Definition, Fourth Edition
System V ABISystem V Application Binary Interface, Edition 4.1http://www.caldera.com/developers/devspecs/gabi41.pdf
System V ABI UpdateSystem V Application Binary Interface - DRAFT - 17 December 2003http://www.caldera.com/developers/gabi/2003-12-17/contents.html
System V Application Binary Interface PowerPC™ Processor SupplementSystem V Application Binary Interface PowerPC™ Processor Supplementhttp://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf
The PowerPC™ Microprocessor FamilyThe PowerPC™ Microprocessor Family: The Programming Environment Manual for 32 and 64-bit Microprocessorshttp://refspecs.linux-foundation.org/PPC_hrm.2005mar31.pdf
X/Open CursesCAE Specification, May 1996, X/Open Curses, Issue 4, Version 2 (ISBN: 1-85912-171-3, C610), plus Corrigendum U018http://www.opengroup.org/publications/catalog/un.htm

2.2. Informative References/Bibliography

In addition, the specifications listed below provide essential background information to implementors of this specification. These references are included for information only.

Table 2-2. Other References

NameTitleURL
DWARF Debugging Information Format, Revision 2.0.0DWARF Debugging Information Format, Revision 2.0.0 (July 27, 1993)http://refspecs.linux-foundation.org/dwarf/dwarf-2.0.0.pdf
DWARF Debugging Information Format, Revision 3.0.0 (Draft)DWARF Debugging Information Format, Revision 3.0.0 (Draft)http://refspecs.linux-foundation.org/dwarf
IEC 60559/IEEE 754 Floating PointIEC 60559:1989 Binary floating-point arithmetic for microprocessor systemshttp://www.ieee.org/
ISO/IEC TR14652ISO/IEC Technical Report 14652:2002 Specification method for cultural conventions
ITU-T V.42International Telecommunication Union Recommendation V.42 (2002): Error-correcting procedures for DCEs using asynchronous-to-synchronous conversionITUVhttp://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-V.42
Li18nux Globalization SpecificationLI18NUX 2000 Globalization Specification, Version 1.0 with Amendment 4http://www.openi18n.org/docs/html/LI18NUX-2000-amd4.htm
Linux Allocated Device RegistryLINUX ALLOCATED DEVICEShttp://www.lanana.org/docs/device-list/devices.txt
PAMOpen Software Foundation, Request For Comments: 86.0 , October 1995, V. Samar & R.Schemers (SunSoft)http://www.opengroup.org/tech/rfc/mirror-rfc/rfc86.0.txt
RFC 1321: The MD5 Message-Digest AlgorithmIETF RFC 1321: The MD5 Message-Digest Algorithmhttp://www.ietf.org/rfc/rfc1321.txt
RFC 1831/1832 RPC & XDRIETF RFC 1831 & 1832http://www.ietf.org/
RFC 1833: Binding Protocols for ONC RPC Version 2IETF RFC 1833: Binding Protocols for ONC RPC Version 2http://www.ietf.org/rfc/rfc1833.txt
RFC 1950: ZLIB Compressed Data Format SpecicationIETF RFC 1950: ZLIB Compressed Data Format Specificationhttp://www.ietf.org/rfc/rfc1950.txt
RFC 1951: DEFLATE Compressed Data Format SpecificationIETF RFC 1951: DEFLATE Compressed Data Format Specification version 1.3http://www.ietf.org/rfc/rfc1951.txt
RFC 1952: GZIP File Format SpecificationIETF RFC 1952: GZIP file format specification version 4.3http://www.ietf.org/rfc/rfc1952.txt
RFC 2440: OpenPGP Message FormatIETF RFC 2440: OpenPGP Message Formathttp://www.ietf.org/rfc/rfc2440.txt
RFC 2821:Simple Mail Transfer ProtocolIETF RFC 2821: Simple Mail Transfer Protocolhttp://www.ietf.org/rfc/rfc2821.txt
RFC 2822:Internet Message FormatIETF RFC 2822: Internet Message Formathttp://www.ietf.org/rfc/rfc2822.txt
RFC 791:Internet ProtocolIETF RFC 791: Internet Protocol Specificationhttp://www.ietf.org/rfc/rfc791.txt
RPM Package FormatRPM Package Format V3.0http://www.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format.html
SUSv2 Commands and UtilitiesThe Single UNIX Specification(SUS) Version 2, Commands and Utilities (XCU), Issue 5 (ISBN: 1-85912-191-8, C604)http://www.opengroup.org/publications/catalog/un.htm
zlib Manualzlib 1.2 Manualhttp://www.gzip.org/zlib/

Chapter 3. Requirements

3.1. Relevant Libraries

The libraries listed in Table 3-1 shall be available on PPC32 Linux Standard Base systems, with the specified runtime names. These names override or supplement the names specified in the generic LSB (ISO/IEC 23360 Part 1) specification. The specified program interpreter, referred to as proginterp in this table, shall be used to load the shared libraries specified by DT_NEEDED entries at run time.

Table 3-1. Standard Library Names

LibraryRuntime Name
libmlibm.so.6
libdllibdl.so.2
libcryptlibcrypt.so.1
libzlibz.so.1
libncurseslibncurses.so.5
libutillibutil.so.1
libclibc.so.6
libpthreadlibpthread.so.0
proginterp/lib/ld-lsb-ppc32.so.3
libgcc_slibgcc_s.so.1

These libraries will be in an implementation-defined directory which the dynamic linker shall search by default.

3.2. LSB Implementation Conformance

A conforming implementation is necessarily architecture specific, and must provide the interfaces specified by both the generic LSB Core specification (ISO/IEC 23360 Part 1) and the relevant architecture specific part of ISO/IEC 23360.

Rationale: An implementation must provide at least the interfaces specified in these specifications. It may also provide additional interfaces.

A conforming implementation shall satisfy the following requirements:

  • A processor architecture represents a family of related processors which may not have identical feature sets. The architecture specific parts of ISO/IEC 23360 that supplement this specification for a given target processor architecture describe a minimum acceptable processor. The implementation shall provide all features of this processor, whether in hardware or through emulation transparent to the application.

  • The implementation shall be capable of executing compiled applications having the format and using the system interfaces described in this document.

  • The implementation shall provide libraries containing the interfaces specified by this document, and shall provide a dynamic linking mechanism that allows these interfaces to be attached to applications at runtime. All the interfaces shall behave as specified in this document.

  • The map of virtual memory provided by the implementation shall conform to the requirements of this document.

  • The implementation's low-level behavior with respect to function call linkage, system traps, signals, and other such activities shall conform to the formats described in this document.

  • The implementation shall provide all of the mandatory interfaces in their entirety.

  • The implementation may provide one or more of the optional interfaces. Each optional interface that is provided shall be provided in its entirety. The product documentation shall state which optional interfaces are provided.

  • The implementation shall provide all files and utilities specified as part of this document in the format defined here and in other referenced documents. All commands and utilities shall behave as required by this document. The implementation shall also provide all mandatory components of an application's runtime environment that are included or referenced in this document.

  • The implementation, when provided with standard data formats and values at a named interface, shall provide the behavior defined for those values and data formats at that interface. However, a conforming implementation may consist of components which are separately packaged and/or sold. For example, a vendor of a conforming implementation might sell the hardware, operating system, and windowing system as separately packaged items.

  • The implementation may provide additional interfaces with different names. It may also provide additional behavior corresponding to data values outside the standard ranges, for standard named interfaces.

3.3. LSB Application Conformance

A conforming application is necessarily architecture specific, and must conform to both the generic LSB Core specification (ISO/IEC 23360 Part 1)and the relevant architecture specific part of ISO/IEC 23360.

A conforming application shall satisfy the following requirements:

  • Its executable files shall be either shell scripts or object files in the format defined for the Object File Format system interface.

  • Its object files shall participate in dynamic linking as defined in the Program Loading and Linking System interface.

  • It shall employ only the instructions, traps, and other low-level facilities defined in the Low-Level System interface as being for use by applications.

  • If it requires any optional interface defined in this document in order to be installed or to execute successfully, the requirement for that optional interface shall be stated in the application's documentation.

  • It shall not use any interface or data format that is not required to be provided by a conforming implementation, unless:

    • If such an interface or data format is supplied by another application through direct invocation of that application during execution, that application shall be in turn an LSB conforming application.

    • The use of that interface or data format, as well as its source, shall be identified in the documentation of the application.

  • It shall not use any values for a named interface that are reserved for vendor extensions.

A strictly conforming application shall not require or use any interface, facility, or implementation-defined extension that is not defined in this document in order to be installed or to execute successfully.

Chapter 4. Definitions

For the purposes of this document, the following definitions, as specified in the ISO/IEC Directives, Part 2, 2001, 4th Edition, apply:

can 

be able to; there is a possibility of; it is possible to

cannot 

be unable to; there is no possibilty of; it is not possible to

may 

is permitted; is allowed; is permissible

need not 

it is not required that; no...is required

shall 

is to; is required to; it is required that; has to; only...is permitted; it is necessary

shall not 

is not allowed [permitted] [acceptable] [permissible]; is required to be not; is required that...be not; is not to be

should 

it is recommended that; ought to

should not 

it is not recommended that; ought not to

Chapter 5. Terminology

For the purposes of this document, the following terms apply:

archLSB

The architectural part of the LSB Specification which describes the specific parts of the interface that are platform specific. The archLSB is complementary to the gLSB.

Binary Standard

The total set of interfaces that are available to be used in the compiled binary code of a conforming application.

gLSB

The common part of the LSB Specification that describes those parts of the interface that remain constant across all hardware implementations of the LSB.

implementation-defined

Describes a value or behavior that is not defined by this document but is selected by an implementor. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence of the value or behavior. An application that relies on such a value or behavior cannot be assured to be portable across conforming implementations. The implementor shall document such a value or behavior so that it can be used correctly by an application.

Shell Script

A file that is read by an interpreter (e.g., awk). The first line of the shell script includes a reference to its interpreter binary.

Source Standard

The set of interfaces that are available to be used in the source code of a conforming application.

undefined

Describes the nature of a value or behavior not defined by this document which results from use of an invalid program construct or invalid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations.

unspecified

Describes the nature of a value or behavior not specified by this document which results from use of a valid program construct or valid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations.

Other terms and definitions used in this document shall have the same meaning as defined in Chapter 3 of the Base Definitions volume of ISO POSIX (2003).

Chapter 6. Documentation Conventions

Throughout this document, the following typographic conventions are used:

function() 

the name of a function

command 

the name of a command or utility

CONSTANT 

a constant value

parameter 

a parameter

variable 

a variable

Throughout this specification, several tables of interfaces are presented. Each entry in these tables has the following format:

name 

the name of the interface

(symver) 

An optional symbol version identifier, if required.

[refno] 

A reference number indexing the table of referenced specifications that follows this table.

For example,

forkpty(GLIBC_2.0) [SUSv3]

refers to the interface named forkpty() with symbol version GLIBC_2.0 that is defined in the SUSv3 reference.

Note: Symbol versions are defined in the architecture specific parts of ISO/IEC 23360 only.

II. Executable And Linking Format (ELF)

Table of Contents
7. Introduction
8. Low Level System Information
8.1. Machine Interface
8.1.1. Processor Architecture
8.1.2. Data Representation
8.2. Function Calling Sequence
8.2.1. CPU Registers
8.2.2. Floating Point Registers
8.2.3. Stack Frame
8.2.4. Arguments
8.2.5. Return Values
8.3. Operating System Interface
8.3.1. Exception Interface
8.3.2. Signal Delivery
8.4. Process Initialization
8.4.1. Special Registers
8.4.2. Process Stack (on entry)
8.4.3. Auxiliary Vector
8.5. Coding Examples
8.5.1. Code Model Overview/Architecture Constraints
8.5.2. Position-Independent Function Prologue
8.5.3. Data Objects
8.5.4. Function Calls
8.5.5. Branching
8.6. C Stack Frame
8.6.1. Variable Argument List
8.6.2. Dynamic Allocation of Stack Space
8.7. Debug Information
9. Object Format
9.1. Introduction
9.2. ELF Header
9.2.1. Machine Information
9.3. Sections
9.3.1. Special Sections
9.3.2. Linux Special Sections
9.4. Symbol Table
9.5. Relocation
9.5.1. Relocation Types
10. Program Loading and Dynamic Linking
10.1. Introduction
10.2. Program Header
10.3. Program Loading
10.4. Dynamic Linking
10.4.1. Dynamic Section
10.4.2. Global Offset Table
10.4.3. Function Addresses
10.4.4. Procedure Linkage Table

Chapter 7. Introduction

Executable and Linking Format (ELF) defines the object format for compiled applications. This specification supplements the information found in System V ABI Update and System V Application Binary Interface PowerPC™ Processor Supplement, and is intended to document additions made since the publication of that document.

Chapter 8. Low Level System Information

8.1. Machine Interface

8.1.1. Processor Architecture

The PowerPC Architecture is specified by the following documents:

Only the features of the PowerPC 603 processor instruction set may be assumed to be present. An application should determine if any additional instruction set features are available before using those additional features. If a feature is not present, then the application may not use it.

Note: The presence of a hardware floating point unit is optional. However, applications requiring floating point arithmetic may experience substantial performance penalties on system without such a unit.

Conforming applications may use only instructions which do not require elevated privileges.

Conforming applications shall not invoke the implementations underlying system call interface directly. The interfaces in the implementation base libraries shall be used instead.

Rationale: Implementation-supplied base libraries may use the system call interface but applications must not assume any particular operating system or kernel version is present.

An implementation must support the 32-bit computation mode as described in The PowerPC™ Microprocessor Family. Conforming applications shall not use instructions provided only for the 64-bit mode.

Applications conforming to this specification must provide feedback to the user if a feature that is required for correct execution of the application is not present. Applications conforming to this specification should attempt to execute in a diminished capacity if a required feature is not present.

This specification does not provide any performance guarantees of a conforming system. A system conforming to this specification may be implemented in either hardware or software.

8.1.2. Data Representation

LSB-conforming applications shall use the data representation as defined in Chapter 3 "Data Representation" section of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.1.2.1. Byte Ordering

LSB-conforming applications shall use big-endian byte ordering. LSB-conforming implementations may support little-endian applications.

8.1.2.2. Fundamental Types

In addition to the fundamental types specified in Chapter 3 "Fundamental Types" section of the System V Application Binary Interface PowerPC™ Processor Supplement, a 64 bit data type is defined here.

Table 8-1. Scalar Types

TypeCsizeofAlignment (bytes)IntelI386 Architecture
Integrallong long88signed double word
signed long long
unsigned long long88unsigned double word

LSB-conforming applications shall not use the long double fundamental type.

8.2. Function Calling Sequence

LSB-conforming applications shall use the function calling sequence as defined in Chapter 3, Section "Function Calling Sequence" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.2.1. CPU Registers

LSB-conforming applications shall use only the registers described in Chapter 3, Section "Function Calling Sequence", Subsection "Registers" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.2.2. Floating Point Registers

LSB-conforming applications shall use only the registers described in Chapter 3, Section "Function Calling Sequence", Subsection "Registers" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.2.3. Stack Frame

LSB-conforming applications shall use stack frames as described in Chapter 3, Section "Function Calling Sequence", Subsection "The Stack Frame" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.2.4. Arguments

LSB-conforming applications shall pass parameters to functions as described in Chapter 3, Section "Function Calling Sequence", Subsection "Parameter Passing" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.2.5. Return Values

LSB-conforming applications shall not return structures or unions in registers as described in Chapter 3, Section "Function Calling Sequence", Subsection "Return Values" of System V Application Binary Interface PowerPC™ Processor Supplement. Instead they must use the alternative method of passing the address of a buffer in a register as shown in the same section.

8.3. Operating System Interface

LSB-conforming applications shall use the Operating System Interfaces as defined in Chapter 3, Section "Operating System Interface" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.3.1. Exception Interface

LSB-conforming applications shall use the Exception Interfaces as defined in Chapter 3, Section "Exception Interface" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.3.1.1. Debugging Support

The LSB does not specify debugging information, however, if the DWARF specification is implemented, see Chapter 3, Section "DWARF Definition" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.3.2. Signal Delivery

LSB-conforming applications shall follow the guidelines defined in Chapter 3, Section "Exception Interface" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.4. Process Initialization

LSB-conforming applications shall use the Process initialization as defined in Chapter 3, Section "Process Initialization" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.4.1. Special Registers

Contrary to what is stated in the Registers part of chapter 3 of the System V Application Binary Interface PowerPC™ Processor Supplement there are no values set in registers r3, r4, r5, r6 and r7. Instead the values specified to appear in all of those registers except r7 are placed on the stack. The value to be placed into register r7, the termination function pointer is not passed to the process.

8.4.2. Process Stack (on entry)

Figure 3-31 in System V Application Binary Interface PowerPC™ Processor Supplement is incorrect. The initial stack must look like the following.

Figure 8-1. Initial Process Stack

8.4.3. Auxiliary Vector

In addition to the types defined in Chapter 3, Section "Process Initialization", Subsection "Process Stack" of the System V Application Binary Interface PowerPC™ Processor Supplement the following are also supported:

Table 8-2. Extra Auxiliary Types

NameValueComment
AT_NOTELF10Program is not ELF
AT_UID11Real uid
AT_EUID12Effective uid
AT_GID13Real gid
AT_EGID14Effective gid
AT_PLATFORM15String identifying CPU for optimizations
AT_HWCAP16Arch dependent hints at CPU capabilities
AT_CLKTCK17Frequency at which times() increments
AT_DCACHEBSIZE19The a_val member of this entry gives the data cache block size for processors on the system on which this program is running. If the processors have unified caches, AT_DCACHEBSIZE is the same as AT_UCACHEBSIZE
AT_ICACHEBSIZE20The a_val member of this entyr gives the instruction cache block size for processors on the system on which this program is running. If the processors have unified caches, AT_DCACHEBSIZE is the same as AT_UCACHEBSIZE.
AT_UCACHEBSIZE21The a_val member of this entry is zero if the processors on the system on which this program is running do not have a unified instruction and data cache. Otherwise it gives the cache block size.
AT_IGNOREPPC22All entries of this type should be ignored.

The last three entries in the table above override the values specified in System V Application Binary Interface PowerPC™ Processor Supplement.

8.5. Coding Examples

LSB-conforming applications may use the coding examples given in Chapter 3, Section "Coding Examples" of the System V Application Binary Interface PowerPC™ Processor Supplement to guide implemention of fundamental operations in the following areas.

8.5.1. Code Model Overview/Architecture Constraints

LSB-Conforming applications may use any of the code models described in Chapter 3, Section "Coding Examples", Subsection "Code Model Overview" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.5.2. Position-Independent Function Prologue

LSB-Conforming applications may use examples described in Chapter 3, Section "Coding Examples", Subsection "Function Prologue and Epilogue" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.5.3. Data Objects

LSB-Conforming applications may use examples described in Chapter 3, Section "Coding Examples", Subsection "Data Objects" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.5.4. Function Calls

LSB-Conforming applications may use examples described in Chapter 3, Section "Coding Examples", Subsection "Function Calls" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.5.5. Branching

LSB-Conforming applications may use examples described in Chapter 3, Section "Coding Examples", Subsection "Branching" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.6. C Stack Frame

8.6.1. Variable Argument List

LSB-Conforming applications shall only use variable arguments to functions in the manner described in Chapter 3, Section "Function Calling Sequence", Subsection "Variable Argument Lists" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.6.2. Dynamic Allocation of Stack Space

LSB-Conforming applications shall follow guidelines discussed in in Chapter 3, Section "Coding Examples", Subsection "Dynamic Stack Space Allocation" of the System V Application Binary Interface PowerPC™ Processor Supplement.

8.7. Debug Information

The LSB does not currently specify the format of Debug information.

Chapter 9. Object Format

9.1. Introduction

LSB-conforming implementations shall support an object file format, called Executable and Linking Format (ELF) as defined by the System V Application Binary Interface PowerPC™ Processor Supplement and as supplemented by the Linux Standard Base Specification and this document. LSB-conforming implementations need not support tags related functionality. LSB-conforming applications must not rely on tags related functionality.

9.2. ELF Header

9.2.1. Machine Information

LSB-conforming applications shall use the Machine Information as defined in System V Application Binary Interface PowerPC™ Processor Supplement, Chapter 4, Section "ELF Header" Subsection "Machine Information".

9.3. Sections

9.3.1. Special Sections

The following sections are defined in the System V Application Binary Interface PowerPC™ Processor Supplement Chapter 4, Section "Section", Subsection "Special Sections".

Table 9-1. ELF Special Sections

NameTypeAttributes
.gotSHT_PROGBITSSHF_ALLOC+SHF_WRITE+SHF_EXECINSTR
.pltSHT_NOBITSSHF_ALLOC+SHF_WRITE+SHF_EXECINSTR
.sdataSHT_PROGBITSSHF_ALLOC+SHF_WRITE

.got 

This section holds the global offset table. See `Coding Examples' in Chapter 3, `Special Sections' in Chapter 4, and `Global Offset Table' in Chapter 5 of the processor supplement for more information.

.plt 

This section holds the procedure linkage table.

.sdata 

This section holds initialized small data that contribute to the program memory image.

Note that the .tags, .taglist and .tagsym sections described in Chapter 4, Section "Sections" System V Application Binary Interface PowerPC™ Processor Supplement are not supported.

9.3.2. Linux Special Sections

The following Linux PPC32 specific sections are defined here.

Table 9-2. Additional Special Sections

NameTypeAttributes
.got2SHT_PROGBITSSHF_ALLOC+SHF_WRITE
.rela.bssSHT_RELASHF_ALLOC
.rela.dynSHT_RELASHF_ALLOC
.rela.gotSHT_RELASHF_ALLOC
.rela.got2SHT_RELASHF_ALLOC
.rela.pltSHT_RELASHF_ALLOC
.rela.sbssSHT_RELASHF_ALLOC
.sbssSHT_NOBITSSHF_ALLOC+SHF_WRITE
.sdata2SHT_PROGBITSSHF_ALLOC

.got2 

This section holds the second level GOT.

.rela.bss 

This section holds RELA type relocation information for the BSS section of a shared library or dynamically linked application.

.rela.dyn 

This section holds RELA type relocation information for all sections of a shared library except the PLT.

.rela.got 

This section holds RELA type relocation information for the GOT section of a shared library or dynamically linked application.

.rela.got2 

This section holds RELA type relocation information for the second level GOT section of a shared library or dynamically linked application.

.rela.plt 

This section holds RELA type relocation information for the PLT section of a shared library or dynamically linked application.

.rela.sbss 

This section holds RELA type relocation information for the SBSS section of a shared library or dynamically linked application.

.sbss 

This section holds uninitialized data that contribute to the program's memory image. The system initializes the data with zeroes when the program begins to run.

.sdata2 

This section holds the second level of initialised small data.

9.4. Symbol Table

LSB-conforming applications shall use the Symbol Table as defined in Chapter 4, Section "Symbol Table" of the System V Application Binary Interface PowerPC™ Processor Supplement.

9.5. Relocation

LSB-conforming applications shall use Relocations as defined in Chapter 4, Section "Relocation" of the System V Application Binary Interface PowerPC™ Processor Supplement.

9.5.1. Relocation Types

LSB-conforming applications shall support the relocation types as defined in the Chapter 4, Section "Relocation" Subsection "Relocation Typles" except for the relocation type R_PPC_ADDR30 as specified in Table 4-8 of System V Application Binary Interface PowerPC™ Processor Supplement.

Chapter 10. Program Loading and Dynamic Linking

10.1. Introduction

LSB-conforming implementations shall support the object file information and system actions that create running programs as specified in the System V ABI, System V Application Binary Interface PowerPC™ Processor Supplement Chapter 5 and as supplemented by the generic Linux Standard Base Specification and this document.

10.2. Program Header

LSB-conforming applications shall support the program header as defined in the System V Application Binary Interface PowerPC™ Processor Supplement Chapter 5, Section "Program Loading".

10.3. Program Loading

LSB-conforming implementations shall map file pages to virtual memory pages as described in Section "Program Loading" of the System V Application Binary Interface PowerPC™ Processor Supplement, Chapter 5.

10.4. Dynamic Linking

LSB-conforming implementations shall provide dynamic linking as specified in Section "Dynamic Linking" of the System V Application Binary Interface PowerPC™ Processor Supplement, Chapter 5.

10.4.1. Dynamic Section

The following dynamic entries are defined in the System V Application Binary Interface PowerPC™ Processor Supplement, Chapter 5, Section "Dynamic Linking".

DT_JMPREL 

This entry is associated with a table of relocation entries for the procedure linkage table. This entry is mandatory both for executable and shared object files

DT_PLTGOT 

This entry's d_ptr member gives the address of the first byte in the procedure linkage table

In addtion the following dynamic entries are also supported:

DT_RELACOUNT 

The number of relative relocations in .rela.dyn

10.4.2. Global Offset Table

LSB-conforming implementations shall support a Global Offset Table as described in Chapter 5, Section "Dynamic Linking" of the System V Application Binary Interface PowerPC™ Processor Supplement.

10.4.3. Function Addresses

Function addresses shall behave as described in Chapter 5, Section "Dynamic Linking", Subsection "Function Addresses" of the System V Application Binary Interface PowerPC™ Processor Supplement.

10.4.4. Procedure Linkage Table

LSB-conforming implementations shall support a Procedure Linkage Table as described in Chapter 5, Section "Dynamic Linking", Subsection "Procedure Linkage Table" of the System V Application Binary Interface PowerPC™ Processor Supplement.

III. Base Libraries

Table of Contents
11. Libraries
11.1. Program Interpreter/Dynamic Linker
11.2. Interfaces for libc
11.2.1. RPC
11.2.2. System Calls
11.2.3. Standard I/O
11.2.4. Signal Handling
11.2.5. Localization Functions
11.2.6. Posix Spawn Option
11.2.7. Posix Advisory Option
11.2.8. Socket Interface
11.2.9. Wide Characters
11.2.10. String Functions
11.2.11. IPC Functions
11.2.12. Regular Expressions
11.2.13. Character Type Functions
11.2.14. Time Manipulation
11.2.15. Terminal Interface Functions
11.2.16. System Database Interface
11.2.17. Language Support
11.2.18. Large File Support
11.2.19. Standard Library
11.3. Data Definitions for libc
11.3.1. ctype.h
11.3.2. dirent.h
11.3.3. errno.h
11.3.4. fcntl.h
11.3.5. fnmatch.h
11.3.6. ftw.h
11.3.7. getopt.h
11.3.8. glob.h
11.3.9. iconv.h
11.3.10. langinfo.h
11.3.11. limits.h
11.3.12. locale.h
11.3.13. net/if.h
11.3.14. netdb.h
11.3.15. netinet/in.h
11.3.16. netinet/ip.h
11.3.17. netinet/tcp.h
11.3.18. netinet/udp.h
11.3.19. nl_types.h
11.3.20. pwd.h
11.3.21. regex.h
11.3.22. rpc/auth.h
11.3.23. rpc/clnt.h
11.3.24. rpc/rpc_msg.h
11.3.25. rpc/svc.h
11.3.26. rpc/types.h
11.3.27. rpc/xdr.h
11.3.28. sched.h
11.3.29. search.h
11.3.30. setjmp.h
11.3.31. signal.h
11.3.32. spawn.h
11.3.33. stddef.h
11.3.34. stdint.h
11.3.35. stdio.h
11.3.36. stdlib.h
11.3.37. sys/file.h
11.3.38. sys/ioctl.h
11.3.39. sys/ipc.h
11.3.40. sys/mman.h
11.3.41. sys/msg.h
11.3.42. sys/param.h
11.3.43. sys/poll.h
11.3.44. sys/resource.h
11.3.45. sys/sem.h
11.3.46. sys/shm.h
11.3.47. sys/socket.h
11.3.48. sys/stat.h
11.3.49. sys/statfs.h
11.3.50. sys/statvfs.h
11.3.51. sys/time.h
11.3.52. sys/timeb.h
11.3.53. sys/times.h
11.3.54. sys/types.h
11.3.55. sys/un.h
11.3.56. sys/utsname.h
11.3.57. sys/wait.h
11.3.58. syslog.h
11.3.59. termios.h
11.3.60. ucontext.h
11.3.61. ulimit.h
11.3.62. unistd.h
11.3.63. utime.h
11.3.64. utmp.h
11.3.65. utmpx.h
11.3.66. wctype.h
11.3.67. wordexp.h
11.4. Interfaces for libm
11.4.1. Math
11.5. Data Definitions for libm
11.5.1. complex.h
11.5.2. fenv.h
11.5.3. math.h
11.6. Interfaces for libpthread
11.6.1. Realtime Threads
11.6.2. Advanced Realtime Threads
11.6.3. Posix Threads
11.6.4. Thread aware versions of libc interfaces
11.7. Data Definitions for libpthread
11.7.1. pthread.h
11.7.2. semaphore.h
11.8. Interfaces for libgcc_s
11.8.1. Unwind Library
11.9. Data Definitions for libgcc_s
11.9.1. unwind.h
11.10. Interface Definitions for libgcc_s
_Unwind_DeleteException -- private C++ error handling method
_Unwind_Find_FDE -- private C++ error handling method
_Unwind_ForcedUnwind -- private C++ error handling method
_Unwind_GetDataRelBase -- private IA64 C++ error handling method
_Unwind_GetGR -- private C++ error handling method
_Unwind_GetIP -- private C++ error handling method
_Unwind_GetLanguageSpecificData -- private C++ error handling method
_Unwind_GetRegionStart -- private C++ error handling method
_Unwind_GetTextRelBase -- private IA64 C++ error handling method
_Unwind_RaiseException -- private C++ error handling method
_Unwind_Resume -- private C++ error handling method
_Unwind_SetGR -- private C++ error handling method
_Unwind_SetIP -- private C++ error handling method
11.11. Interfaces for libdl
11.11.1. Dynamic Loader
11.12. Data Definitions for libdl
11.12.1. dlfcn.h
11.13. Interfaces for libcrypt
11.13.1. Encryption

Chapter 11. Libraries

An LSB-conforming implementation shall support base libraries which provide interfaces for accessing the operating system, processor and other hardware in the system.

Only those interfaces that are unique to the PowerPC 32 platform are defined here. This section should be used in conjunction with the corresponding section in the generic Linux Standard Base Core Specification.

11.1. Program Interpreter/Dynamic Linker

The Program Interpreter shall be /lib/ld-lsb-ppc32.so.3.

11.2. Interfaces for libc

Table 11-1 defines the library name and shared object name for the libc library

Table 11-1. libc Definition

Library:libc
SONAME:libc.so.6

The behavior of the interfaces in this library is specified by the following specifications:

[LFS] Large File Support
[LSB] ISO/IEC 23360 Part 1
[SUSv2] SUSv2
[SUSv3] ISO POSIX (2003)
[SVID.3] SVID Issue 3
[SVID.4] SVID Issue 4

11.2.1. RPC

11.2.1.1. Interfaces for RPC

An LSB conforming implementation shall provide the architecture specific functions for RPC specified in Table 11-2, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-2. libc - RPC Function Interfaces

authnone_create(GLIBC_2.0) [SVID.4]clnt_create(GLIBC_2.0) [SVID.4]clnt_pcreateerror(GLIBC_2.0) [SVID.4]clnt_perrno(GLIBC_2.0) [SVID.4]
clnt_perror(GLIBC_2.0) [SVID.4]clnt_spcreateerror(GLIBC_2.0) [SVID.4]clnt_sperrno(GLIBC_2.0) [SVID.4]clnt_sperror(GLIBC_2.0) [SVID.4]
key_decryptsession(GLIBC_2.1) [SVID.3]pmap_getport(GLIBC_2.0) [LSB]pmap_set(GLIBC_2.0) [LSB]pmap_unset(GLIBC_2.0) [LSB]
svc_getreqset(GLIBC_2.0) [SVID.3]svc_register(GLIBC_2.0) [LSB]svc_run(GLIBC_2.0) [LSB]svc_sendreply(GLIBC_2.0) [LSB]
svcerr_auth(GLIBC_2.0) [SVID.3]svcerr_decode(GLIBC_2.0) [SVID.3]svcerr_noproc(GLIBC_2.0) [SVID.3]svcerr_noprog(GLIBC_2.0) [SVID.3]
svcerr_progvers(GLIBC_2.0) [SVID.3]svcerr_systemerr(GLIBC_2.0) [SVID.3]svcerr_weakauth(GLIBC_2.0) [SVID.3]svctcp_create(GLIBC_2.0) [LSB]
svcudp_create(GLIBC_2.0) [LSB]xdr_accepted_reply(GLIBC_2.0) [SVID.3]xdr_array(GLIBC_2.0) [SVID.3]xdr_bool(GLIBC_2.0) [SVID.3]
xdr_bytes(GLIBC_2.0) [SVID.3]xdr_callhdr(GLIBC_2.0) [SVID.3]xdr_callmsg(GLIBC_2.0) [SVID.3]xdr_char(GLIBC_2.0) [SVID.3]
xdr_double(GLIBC_2.0) [SVID.3]xdr_enum(GLIBC_2.0) [SVID.3]xdr_float(GLIBC_2.0) [SVID.3]xdr_free(GLIBC_2.0) [SVID.3]
xdr_int(GLIBC_2.0) [SVID.3]xdr_long(GLIBC_2.0) [SVID.3]xdr_opaque(GLIBC_2.0) [SVID.3]xdr_opaque_auth(GLIBC_2.0) [SVID.3]
xdr_pointer(GLIBC_2.0) [SVID.3]xdr_reference(GLIBC_2.0) [SVID.3]xdr_rejected_reply(GLIBC_2.0) [SVID.3]xdr_replymsg(GLIBC_2.0) [SVID.3]
xdr_short(GLIBC_2.0) [SVID.3]xdr_string(GLIBC_2.0) [SVID.3]xdr_u_char(GLIBC_2.0) [SVID.3]xdr_u_int(GLIBC_2.0) [LSB]
xdr_u_long(GLIBC_2.0) [SVID.3]xdr_u_short(GLIBC_2.0) [SVID.3]xdr_union(GLIBC_2.0) [SVID.3]xdr_vector(GLIBC_2.0) [SVID.3]
xdr_void(GLIBC_2.0) [SVID.3]xdr_wrapstring(GLIBC_2.0) [SVID.3]xdrmem_create(GLIBC_2.0) [SVID.3]xdrrec_create(GLIBC_2.0) [SVID.3]
xdrrec_eof(GLIBC_2.0) [SVID.3]xdrstdio_create(GLIBC_2.0) [LSB]  

11.2.2. System Calls

11.2.2.1. Interfaces for System Calls

An LSB conforming implementation shall provide the architecture specific functions for System Calls specified in Table 11-3, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-3. libc - System Calls Function Interfaces

__fxstat(GLIBC_2.0) [LSB]__getpgid(GLIBC_2.0) [LSB]__lxstat(GLIBC_2.0) [LSB]__xmknod(GLIBC_2.0) [LSB]
__xstat(GLIBC_2.0) [LSB]access(GLIBC_2.0) [SUSv3]acct(GLIBC_2.0) [LSB]alarm(GLIBC_2.0) [SUSv3]
brk(GLIBC_2.0) [SUSv2]chdir(GLIBC_2.0) [SUSv3]chmod(GLIBC_2.0) [SUSv3]chown(GLIBC_2.1) [SUSv3]
chroot(GLIBC_2.0) [SUSv2]clock(GLIBC_2.0) [SUSv3]close(GLIBC_2.0) [SUSv3]closedir(GLIBC_2.0) [SUSv3]
creat(GLIBC_2.0) [SUSv3]dup(GLIBC_2.0) [SUSv3]dup2(GLIBC_2.0) [SUSv3]execl(GLIBC_2.0) [SUSv3]
execle(GLIBC_2.0) [SUSv3]execlp(GLIBC_2.0) [SUSv3]execv(GLIBC_2.0) [SUSv3]execve(GLIBC_2.0) [SUSv3]
execvp(GLIBC_2.0) [SUSv3]exit(GLIBC_2.0) [SUSv3]fchdir(GLIBC_2.0) [SUSv3]fchmod(GLIBC_2.0) [SUSv3]
fchown(GLIBC_2.0) [SUSv3]fcntl(GLIBC_2.0) [LSB]fdatasync(GLIBC_2.0) [SUSv3]flock(GLIBC_2.0) [LSB]
fork(GLIBC_2.0) [SUSv3]fstatfs(GLIBC_2.0) [LSB]fstatvfs(GLIBC_2.1) [SUSv3]fsync(GLIBC_2.0) [SUSv3]
ftime(GLIBC_2.0) [SUSv3]ftruncate(GLIBC_2.0) [SUSv3]getcontext(GLIBC_2.3.4) [SUSv3]getdtablesize(GLIBC_2.0) [LSB]
getegid(GLIBC_2.0) [SUSv3]geteuid(GLIBC_2.0) [SUSv3]getgid(GLIBC_2.0) [SUSv3]getgroups(GLIBC_2.0) [SUSv3]
getitimer(GLIBC_2.0) [SUSv3]getloadavg(GLIBC_2.2) [LSB]getpagesize(GLIBC_2.0) [LSB]getpgid(GLIBC_2.0) [SUSv3]
getpgrp(GLIBC_2.0) [SUSv3]getpid(GLIBC_2.0) [SUSv3]getppid(GLIBC_2.0) [SUSv3]getpriority(GLIBC_2.0) [SUSv3]
getrlimit(GLIBC_2.2) [SUSv3]getrusage(GLIBC_2.0) [SUSv3]getsid(GLIBC_2.0) [SUSv3]getuid(GLIBC_2.0) [SUSv3]
getwd(GLIBC_2.0) [SUSv3]initgroups(GLIBC_2.0) [LSB]ioctl(GLIBC_2.0) [LSB]kill(GLIBC_2.0) [LSB]
killpg(GLIBC_2.0) [SUSv3]lchown(GLIBC_2.0) [SUSv3]link(GLIBC_2.0) [LSB]lockf(GLIBC_2.0) [SUSv3]
lseek(GLIBC_2.0) [SUSv3]mkdir(GLIBC_2.0) [SUSv3]mkfifo(GLIBC_2.0) [SUSv3]mlock(GLIBC_2.0) [SUSv3]
mlockall(GLIBC_2.0) [SUSv3]mmap(GLIBC_2.0) [SUSv3]mprotect(GLIBC_2.0) [SUSv3]mremap(GLIBC_2.0) [LSB]
msync(GLIBC_2.0) [SUSv3]munlock(GLIBC_2.0) [SUSv3]munlockall(GLIBC_2.0) [SUSv3]munmap(GLIBC_2.0) [SUSv3]
nanosleep(GLIBC_2.0) [SUSv3]nice(GLIBC_2.0) [SUSv3]open(GLIBC_2.0) [SUSv3]opendir(GLIBC_2.0) [SUSv3]
pathconf(GLIBC_2.0) [SUSv3]pause(GLIBC_2.0) [SUSv3]pipe(GLIBC_2.0) [SUSv3]poll(GLIBC_2.0) [SUSv3]
pselect(GLIBC_2.0) [SUSv3]read(GLIBC_2.0) [SUSv3]readdir(GLIBC_2.0) [SUSv3]readdir_r(GLIBC_2.0) [SUSv3]
readlink(GLIBC_2.0) [SUSv3]readv(GLIBC_2.0) [SUSv3]rename(GLIBC_2.0) [SUSv3]rmdir(GLIBC_2.0) [SUSv3]
sbrk(GLIBC_2.0) [SUSv2]sched_get_priority_max(GLIBC_2.0) [SUSv3]sched_get_priority_min(GLIBC_2.0) [SUSv3]sched_getparam(GLIBC_2.0) [SUSv3]
sched_getscheduler(GLIBC_2.0) [SUSv3]sched_rr_get_interval(GLIBC_2.0) [SUSv3]sched_setparam(GLIBC_2.0) [SUSv3]sched_setscheduler(GLIBC_2.0) [LSB]
sched_yield(GLIBC_2.0) [SUSv3]select(GLIBC_2.0) [SUSv3]setcontext(GLIBC_2.3.4) [SUSv3]setegid(GLIBC_2.0) [SUSv3]
seteuid(GLIBC_2.0) [SUSv3]setgid(GLIBC_2.0) [SUSv3]setitimer(GLIBC_2.0) [SUSv3]setpgid(GLIBC_2.0) [SUSv3]
setpgrp(GLIBC_2.0) [SUSv3]setpriority(GLIBC_2.0) [SUSv3]setregid(GLIBC_2.0) [SUSv3]setreuid(GLIBC_2.0) [SUSv3]
setrlimit(GLIBC_2.2) [SUSv3]setrlimit64(GLIBC_2.1) [LFS]setsid(GLIBC_2.0) [SUSv3]setuid(GLIBC_2.0) [SUSv3]
sleep(GLIBC_2.0) [SUSv3]statfs(GLIBC_2.0) [LSB]statvfs(GLIBC_2.1) [SUSv3]stime(GLIBC_2.0) [LSB]
symlink(GLIBC_2.0) [SUSv3]sync(GLIBC_2.0) [SUSv3]sysconf(GLIBC_2.0) [LSB]time(GLIBC_2.0) [SUSv3]
times(GLIBC_2.0) [SUSv3]truncate(GLIBC_2.0) [SUSv3]ulimit(GLIBC_2.0) [SUSv3]umask(GLIBC_2.0) [SUSv3]
uname(GLIBC_2.0) [SUSv3]unlink(GLIBC_2.0) [LSB]utime(GLIBC_2.0) [SUSv3]utimes(GLIBC_2.0) [SUSv3]
vfork(GLIBC_2.0) [SUSv3]wait(GLIBC_2.0) [SUSv3]wait4(GLIBC_2.0) [LSB]waitid(GLIBC_2.1) [SUSv3]
waitpid(GLIBC_2.0) [LSB]write(GLIBC_2.0) [SUSv3]writev(GLIBC_2.0) [SUSv3] 

An LSB conforming implementation shall provide the architecture specific deprecated functions for System Calls specified in Table 11-4, with the full mandatory functionality as described in the referenced underlying specification.

Note: These interfaces are deprecated, and applications should avoid using them. These interfaces may be withdrawn in future releases of this specification.

Table 11-4. libc - System Calls Deprecated Function Interfaces

fstatfs(GLIBC_2.0) [LSB]getdtablesize(GLIBC_2.0) [LSB]getpagesize(GLIBC_2.0) [LSB]getwd(GLIBC_2.0) [SUSv3]
statfs(GLIBC_2.0) [LSB]   

11.2.3. Standard I/O

11.2.3.1. Interfaces for Standard I/O

An LSB conforming implementation shall provide the architecture specific functions for Standard I/O specified in Table 11-5, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-5. libc - Standard I/O Function Interfaces

_IO_feof(GLIBC_2.0) [LSB]_IO_getc(GLIBC_2.0) [LSB]_IO_putc(GLIBC_2.0) [LSB]_IO_puts(GLIBC_2.0) [LSB]
asprintf(GLIBC_2.0) [LSB]clearerr(GLIBC_2.0) [SUSv3]ctermid(GLIBC_2.0) [SUSv3]fclose(GLIBC_2.1) [SUSv3]
fdopen(GLIBC_2.1) [SUSv3]feof(GLIBC_2.0) [SUSv3]ferror(GLIBC_2.0) [SUSv3]fflush(GLIBC_2.0) [SUSv3]
fflush_unlocked(GLIBC_2.0) [LSB]fgetc(GLIBC_2.0) [SUSv3]fgetpos(GLIBC_2.2) [SUSv3]fgets(GLIBC_2.0) [SUSv3]
fgetwc_unlocked(GLIBC_2.2) [LSB]fileno(GLIBC_2.0) [SUSv3]flockfile(GLIBC_2.0) [SUSv3]fopen(GLIBC_2.1) [SUSv3]
fprintf(GLIBC_2.0) [SUSv3]fputc(GLIBC_2.0) [SUSv3]fputs(GLIBC_2.0) [SUSv3]fread(GLIBC_2.0) [SUSv3]
freopen(GLIBC_2.0) [SUSv3]fscanf(GLIBC_2.0) [LSB]fseek(GLIBC_2.0) [SUSv3]fseeko(GLIBC_2.1) [SUSv3]
fsetpos(GLIBC_2.2) [SUSv3]ftell(GLIBC_2.0) [SUSv3]ftello(GLIBC_2.1) [SUSv3]fwrite(GLIBC_2.0) [SUSv3]
getc(GLIBC_2.0) [SUSv3]getc_unlocked(GLIBC_2.0) [SUSv3]getchar(GLIBC_2.0) [SUSv3]getchar_unlocked(GLIBC_2.0) [SUSv3]
getw(GLIBC_2.0) [SUSv2]pclose(GLIBC_2.1) [SUSv3]popen(GLIBC_2.1) [SUSv3]printf(GLIBC_2.0) [SUSv3]
putc(GLIBC_2.0) [SUSv3]putc_unlocked(GLIBC_2.0) [SUSv3]putchar(GLIBC_2.0) [SUSv3]putchar_unlocked(GLIBC_2.0) [SUSv3]
puts(GLIBC_2.0) [SUSv3]putw(GLIBC_2.0) [SUSv2]remove(GLIBC_2.0) [SUSv3]rewind(GLIBC_2.0) [SUSv3]
rewinddir(GLIBC_2.0) [SUSv3]scanf(GLIBC_2.0) [LSB]seekdir(GLIBC_2.0) [SUSv3]setbuf(GLIBC_2.0) [SUSv3]
setbuffer(GLIBC_2.0) [LSB]setvbuf(GLIBC_2.0) [SUSv3]snprintf(GLIBC_2.0) [SUSv3]sprintf(GLIBC_2.0) [SUSv3]
sscanf(GLIBC_2.0) [LSB]telldir(GLIBC_2.0) [SUSv3]tempnam(GLIBC_2.0) [SUSv3]ungetc(GLIBC_2.0) [SUSv3]
vasprintf(GLIBC_2.0) [LSB]vdprintf(GLIBC_2.0) [LSB]vfprintf(GLIBC_2.0) [SUSv3]vprintf(GLIBC_2.0) [SUSv3]
vsnprintf(GLIBC_2.0) [SUSv3]vsprintf(GLIBC_2.0) [SUSv3]  

An LSB conforming implementation shall provide the architecture specific data interfaces for Standard I/O specified in Table 11-6, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-6. libc - Standard I/O Data Interfaces

stderr(GLIBC_2.0) [SUSv3]stdin(GLIBC_2.0) [SUSv3]stdout(GLIBC_2.0) [SUSv3] 

11.2.4. Signal Handling

11.2.4.1. Interfaces for Signal Handling

An LSB conforming implementation shall provide the architecture specific functions for Signal Handling specified in Table 11-7, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-7. libc - Signal Handling Function Interfaces

__libc_current_sigrtmax(GLIBC_2.1) [LSB]__libc_current_sigrtmin(GLIBC_2.1) [LSB]__sigsetjmp(GLIBC_2.3.4) [LSB]__sysv_signal(GLIBC_2.0) [LSB]
__xpg_sigpause(GLIBC_2.2) [LSB]bsd_signal(GLIBC_2.0) [SUSv3]psignal(GLIBC_2.0) [LSB]raise(GLIBC_2.0) [SUSv3]
sigaction(GLIBC_2.0) [SUSv3]sigaddset(GLIBC_2.0) [SUSv3]sigaltstack(GLIBC_2.0) [SUSv3]sigandset(GLIBC_2.0) [LSB]
sigdelset(GLIBC_2.0) [SUSv3]sigemptyset(GLIBC_2.0) [SUSv3]sigfillset(GLIBC_2.0) [SUSv3]sighold(GLIBC_2.1) [SUSv3]
sigignore(GLIBC_2.1) [SUSv3]siginterrupt(GLIBC_2.0) [SUSv3]sigisemptyset(GLIBC_2.0) [LSB]sigismember(GLIBC_2.0) [SUSv3]
siglongjmp(GLIBC_2.3.4) [SUSv3]signal(GLIBC_2.0) [SUSv3]sigorset(GLIBC_2.0) [LSB]sigpause(GLIBC_2.0) [LSB]
sigpending(GLIBC_2.0) [SUSv3]sigprocmask(GLIBC_2.0) [SUSv3]sigqueue(GLIBC_2.1) [SUSv3]sigrelse(GLIBC_2.1) [SUSv3]
sigreturn(GLIBC_2.0) [LSB]sigset(GLIBC_2.1) [SUSv3]sigsuspend(GLIBC_2.0) [SUSv3]sigtimedwait(GLIBC_2.1) [SUSv3]
sigwait(GLIBC_2.0) [SUSv3]sigwaitinfo(GLIBC_2.1) [SUSv3]  

An LSB conforming implementation shall provide the architecture specific deprecated functions for Signal Handling specified in Table 11-8, with the full mandatory functionality as described in the referenced underlying specification.

Note: These interfaces are deprecated, and applications should avoid using them. These interfaces may be withdrawn in future releases of this specification.

Table 11-8. libc - Signal Handling Deprecated Function Interfaces

sigpause(GLIBC_2.0) [LSB]   

An LSB conforming implementation shall provide the architecture specific data interfaces for Signal Handling specified in Table 11-9, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-9. libc - Signal Handling Data Interfaces

_sys_siglist(GLIBC_2.3.3) [LSB]   

11.2.5. Localization Functions

11.2.5.1. Interfaces for Localization Functions

An LSB conforming implementation shall provide the architecture specific functions for Localization Functions specified in Table 11-10, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-10. libc - Localization Functions Function Interfaces

bind_textdomain_codeset(GLIBC_2.2) [LSB]bindtextdomain(GLIBC_2.0) [LSB]catclose(GLIBC_2.0) [SUSv3]catgets(GLIBC_2.0) [SUSv3]
catopen(GLIBC_2.0) [SUSv3]dcgettext(GLIBC_2.0) [LSB]dcngettext(GLIBC_2.2) [LSB]dgettext(GLIBC_2.0) [LSB]
dngettext(GLIBC_2.2) [LSB]gettext(GLIBC_2.0) [LSB]iconv(GLIBC_2.1) [SUSv3]iconv_close(GLIBC_2.1) [SUSv3]
iconv_open(GLIBC_2.1) [SUSv3]localeconv(GLIBC_2.2) [SUSv3]ngettext(GLIBC_2.2) [LSB]nl_langinfo(GLIBC_2.0) [SUSv3]
setlocale(GLIBC_2.0) [SUSv3]textdomain(GLIBC_2.0) [LSB]  

An LSB conforming implementation shall provide the architecture specific data interfaces for Localization Functions specified in Table 11-11, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-11. libc - Localization Functions Data Interfaces

_nl_msg_cat_cntr(GLIBC_2.0) [LSB]   

11.2.6. Posix Spawn Option

11.2.6.1. Interfaces for Posix Spawn Option

An LSB conforming implementation shall provide the architecture specific functions for Posix Spawn Option specified in Table 11-12, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-12. libc - Posix Spawn Option Function Interfaces

posix_spawn(GLIBC_2.2) [SUSv3]posix_spawn_file_actions_addclose(GLIBC_2.2) [SUSv3]posix_spawn_file_actions_adddup2(GLIBC_2.2) [SUSv3]posix_spawn_file_actions_addopen(GLIBC_2.2) [SUSv3]
posix_spawn_file_actions_destroy(GLIBC_2.2) [SUSv3]posix_spawn_file_actions_init(GLIBC_2.2) [SUSv3]posix_spawnattr_destroy(GLIBC_2.2) [SUSv3]posix_spawnattr_getflags(GLIBC_2.2) [SUSv3]
posix_spawnattr_getpgroup(GLIBC_2.2) [SUSv3]posix_spawnattr_getschedparam(GLIBC_2.2) [SUSv3]posix_spawnattr_getschedpolicy(GLIBC_2.2) [SUSv3]posix_spawnattr_getsigdefault(GLIBC_2.2) [SUSv3]
posix_spawnattr_getsigmask(GLIBC_2.2) [SUSv3]posix_spawnattr_init(GLIBC_2.2) [SUSv3]posix_spawnattr_setflags(GLIBC_2.2) [SUSv3]posix_spawnattr_setpgroup(GLIBC_2.2) [SUSv3]
posix_spawnattr_setschedparam(GLIBC_2.2) [SUSv3]posix_spawnattr_setschedpolicy(GLIBC_2.2) [SUSv3]posix_spawnattr_setsigdefault(GLIBC_2.2) [SUSv3]posix_spawnattr_setsigmask(GLIBC_2.2) [SUSv3]
posix_spawnp(GLIBC_2.2) [SUSv3]   

11.2.7. Posix Advisory Option

11.2.7.1. Interfaces for Posix Advisory Option

An LSB conforming implementation shall provide the architecture specific functions for Posix Advisory Option specified in Table 11-13, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-13. libc - Posix Advisory Option Function Interfaces

posix_fadvise(GLIBC_2.2) [SUSv3]posix_fallocate(GLIBC_2.2) [SUSv3]posix_madvise(GLIBC_2.2) [SUSv3]posix_memalign(GLIBC_2.2) [SUSv3]

11.2.8. Socket Interface

11.2.8.1. Interfaces for Socket Interface

An LSB conforming implementation shall provide the architecture specific functions for Socket Interface specified in Table 11-14, with the full mandatory functionality as described in the referenced underlying specification.

Table 11-14. libc - Socket Interface Function Interfaces

__h_errno_location(GLIBC_2.0) [LSB]accept(GLIBC_2.0) [SUSv3]bind(GLIBC_2.0) [SUSv3]bindresvport(GLIBC_2.0) [LSB]
connect(GLIBC_2.0) [SUSv3]gethostid(GLIBC_2.0) [SUSv3]gethostname(GLIBC_2.0) [SUSv3]getpeername(GLIBC_2.0) [SUSv3]
getsockname(GLIBC_2.0) [SUSv3]getsockopt(GLIBC_2.0) [LSB]if_freenameindex(GLIBC_2.1) [SUSv3]if_indextoname(GLIBC_2.1) [SUSv3]
if_nameindex(GLIBC_2.1) [SUSv3]if_nametoindex(GLIBC_2.1) [SUSv3]listen(GLIBC_2.0) [SUSv3]recv(GLIBC_2.0) [SUSv3]
recvfrom(GLIBC_2.0) [SUSv3]recvmsg(GLIBC_2.0) [SUSv3]send(GLIBC_2.0) [SUSv3]sendmsg(GLIBC_2.0) [SUSv3]
sendto(GLIBC_2.0) [SUSv3]setsockopt(GLIBC_2.0) [LSB]shutdown(GLIBC_2.0) [SUSv3]sockatmark(GLIBC_2.2.4) [SUSv3]
socket(GLIBC_2.0) [SUSv3]socketpair(GLIBC_2.0) [SUSv3]  

An LSB conforming implementation shall provide the a