Linux Standard Base Core Module Specification for IA64 2.0 Copyright ? 2004 Free Standards Group 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 are 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 These excerpts are being used in accordance with their respective licenses. Linux is a trademark of Linus Torvalds. UNIX a registered trademark of the Open Group in the United States and other countries. LSB is a trademark of the Free Standards Group in the USA and other countries. AMD is a trademark of Advanced Micro Devices, Inc. Intel and Itanium are registered trademarks and Intel386 is a trademarks of Intel Corporation. OpenGL is a registered trademark of Silicon Graphics, Inc. Table of Contents Specification Introduction ELF Specification Linux Standard Base Specification Linux Packaging Specification Specification Introduction ------------------------------------------------------------------------------- Table of Contents Foreword Introduction I. Introductory Elements 1. Scope General Module Specific Scope 2. Normative References 3. Requirements Relevant Libraries LSB Implementation Conformance LSB Application Conformance 4. Definitions 5. Terminology List of Tables 2-1. Normative References 3-1. Standard Library Names ------------------------------------------------------------------------------- Foreword This is version 2.0 of the Linux Standard Base Core Module Specification for IA64. An implementation of this version of the specification may not claim to be an implementation of the Linux Standard Base unless it has successfully completed the compliance process as defined by the Free Standards Group. ------------------------------------------------------------------------------- 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. I. Introductory Elements Table of Contents 1. Scope 2. Normative References 3. Requirements 4. Definitions 5. Terminology ------------------------------------------------------------------------------- Chapter 1. Scope 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") describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific specification ("LSB-arch") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the architecture-specific supplement for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. The LSB-generic document shall be used in conjunction with an architecture-specific supplement. Whenever a section of the LSB-generic specification shall be supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture supplement. Architecture supplements 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 shall provide 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. ------------------------------------------------------------------------------- Module Specific Scope This is the Itanium architecture specific Core module of the Linux Standards Base (LSB). This module supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this module are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core. ------------------------------------------------------------------------------- Chapter 2. Normative References The specifications listed below are referenced in whole or in part by the Linux Standard Base. In this specification, where only a particular section of one of these references is identified, then the normative reference is to that section alone, and the rest of the referenced document is informative. Table 2-1. Normative References +-----------------------------------------------------------------------------+ |System V Application Binary Interface - DRAFT - |http://www.caldera.com/ | |17 December 2003 |developers/gabi/2003-12-17/ | | |contents.html | |------------------------------------------------+----------------------------| |DWARF Debugging Information Format, Revision |http://www.eagercon.com/ | |2.0.0 (July 27, 1993) |dwarf/dwarf-2.0.0.pdf | |------------------------------------------------+----------------------------| |Filesystem Hierarchy Standard (FHS) 2.3 |http://www.pathname.com/fhs/| |------------------------------------------------+----------------------------| |IEEE Standard 754 for Binary Floating-Point |http://www.ieee.org/ | |Arithmetic | | |------------------------------------------------+----------------------------| |System V Application Binary Interface, Edition |http://www.caldera.com/ | |4.1 |developers/devspecs/ | | |gabi41.pdf | |------------------------------------------------+----------------------------| |Intel Itanium ? Processor-specific Application |http:// | |Binary Interface |refspecs.freestandards.org/ | | |elf/IA64-SysV-psABI.pdf | |------------------------------------------------+----------------------------| |Itanium ? Software Conventions & Runtime |http:// | |Architecture Guide |refspecs.freestandards.org/ | | |IA64conventions.pdf | |------------------------------------------------+----------------------------| |Itanium ? Architecture Software Developer's |http:// | |Manual Volume 1: Application Architecture |refspecs.freestandards.org/ | | |IA64-softdevman-vol1.pdf | |------------------------------------------------+----------------------------| |Itanium ? Architecture Software Developer's |http:// | |Manual Volume 2: System Architecture |refspecs.freestandards.org/ | | |IA64-softdevman-vol2.pdf | |------------------------------------------------+----------------------------| |Itanium ? Architecture Software Developer's |http:// | |Manual Volume 3: Instruction Set Reference |refspecs.freestandards.org/ | | |IA64-softdevman-vol3.pdf | |------------------------------------------------+----------------------------| |IA-64 Processor Reference: Intel Itanium ? |http:// | |Processor Reference Manual for Software |refspecs.freestandards.org/ | |Development |IA64-softdevman-vol4.pdf | |------------------------------------------------+----------------------------| |ISO/IEC 9899: 1999, Programming Languages --C | | |------------------------------------------------+----------------------------| |Linux Assigned Names And Numbers Authority |http://www.lanana.org/ | |------------------------------------------------+----------------------------| | |http://www.UNIX-systems.org/| |Large File Support |version2/whatsnew/ | | |lfs20mar.html | |------------------------------------------------+----------------------------| |LI18NUX 2000 Globalization Specification, |http://www.li18nux.org/docs/| |Version 1.0 with Amendment 4 |html/LI18NUX-2000-amd4.htm | |------------------------------------------------+----------------------------| |Linux Standard Base |http://www.linuxbase.org/ | | |spec/ | |------------------------------------------------+----------------------------| | |http://www.opengroup.org/ | |OSF-RFC 86.0 |tech/rfc/mirror-rfc/ | | |rfc86.0.txt | |------------------------------------------------+----------------------------| |RFC 1833: Binding Protocols for ONC RPC Version |http://www.ietf.org/rfc/ | |2 |rfc1833.txt | |------------------------------------------------+----------------------------| |RFC 1952: GZIP file format specification version|http://www.ietf.org/rfc/ | |4.3 |rfc1952.txt | |------------------------------------------------+----------------------------| |RFC 2440: OpenPGP Message Format |http://www.ietf.org/rfc/ | | |rfc2440.txt | |------------------------------------------------+----------------------------| |CAE Specification, May 1996, X/Open Curses, |http://www.opengroup.org/ | |Issue 4, Version 2 (ISBN: 1-85912-171-3, C610), |publications/catalog/un.htm | |plus Corrigendum U018 | | |------------------------------------------------+----------------------------| |The Single UNIX Specification(SUS) Version 2, |http://www.opengroup.org/ | |Commands and Utilities (XCU), Issue 5 (ISBN: |publications/catalog/un.htm | |1-85912-191-8, C604) | | |------------------------------------------------+----------------------------| |CAE Specification, January 1997, System |http://www.opengroup.org/ | |Interfaces and Headers (XSH),Issue 5 (ISBN: |publications/catalog/un.htm | |1-85912-181-0, C606) | | |------------------------------------------------+----------------------------| |ISO/IEC 9945:2003 Portable Operating System |http://www.unix.org/version3| |(POSIX)and The Single UNIX Specification(SUS) |/ | |V3 | | |------------------------------------------------+----------------------------| |System V Interface Definition, Issue 3 (ISBN | | |0201566524) | | |------------------------------------------------+----------------------------| |System V Interface Definition,Fourth Edition | | |------------------------------------------------+----------------------------| |zlib 1.2 Manual |http://www.gzip.org/zlib/ | +-----------------------------------------------------------------------------+ ------------------------------------------------------------------------------- Chapter 3. Requirements Relevant Libraries The libraries listed in Table 3-1 shall be available on IA64 Linux Standard Base systems, with the specified runtime names. These names override or supplement the names specified in the generic LSB 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 +--------------------------------+ | Library | Runtime Name | |----------+---------------------| |libm |libm.so.6.1 | |----------+---------------------| |libdl |libdl.so.2 | |----------+---------------------| |libcrypt |libcrypt.so.1 | |----------+---------------------| |libz |libz.so.1 | |----------+---------------------| |libncurses|libncurses.so.5 | |----------+---------------------| |libutil |libutil.so.1 | |----------+---------------------| |libc |libc.so.6.1 | |----------+---------------------| |libpthread|libpthread.so.0 | |----------+---------------------| |proginterp|/lib/ld-lsb-ia64.so.2| |----------+---------------------| |libgcc_s |libgcc_s.so.1 | +--------------------------------+ These libraries will be in an implementation-defined directory which the dynamic linker shall search by default. ------------------------------------------------------------------------------- LSB Implementation Conformance An implementation shall satisfy the following requirements: * The implementation shall implement fully the architecture described in the hardware manual for the target processor architecture. * 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. ------------------------------------------------------------------------------- LSB Application Conformance An application shall satisfy the following requirements: * Its executable files are either shell scripts or object files in the format defined for the Object File Format system interface. * Its object files participate in dynamic linking as defined in the Program Loading and Linking System interface. * It employs 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 is stated in the application's documentation. * It does 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 is in turn an LSB conforming application. + The use of that interface or data format, as well as its source, is 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 does 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. ELF Specification ------------------------------------------------------------------------------- Table of Contents I. Low Level System Information 1. Machine Interface Processor Architecture Data Representation 2. Function Calling Sequence CPU Registers Floating Point Registers Stack Frame Arguments Return Values 3. Operating System Interface Processor Execution Mode Exception Interface Signal Delivery 4. Process Initialization Special Registers Process Stack (on entry) Auxiliary Vector Environment 5. Coding Examples Code Model Overview/Architecture Constraints Position-Independent Function Prologue Data Objects Function Calls Branching 6. C Stack Frame Variable Argument List Dynamic Allocation of Stack Space 7. Debug Information II. Object Format 8. ELF Header Machine Information 9. Sections Special Sections Linux Special Sections Section Types Section Attribute Flags Special Section Types 10. Symbol Table 11. Relocation Relocation Types III. Program Loading and Dynamic Linking 12. Program Header Types Flags 13. Program Loading 14. Dynamic Linking Dynamic Entries Global Offset Table Shared Object Dependencies Function Addresses Procedure Linkage Table Initialization and Termination Functions List of Tables 1-1. Scalar Types 8-1. Additional Processor-Specific Flags 9-1. ELF Special Sections 9-2. Additional Special Sections List of Figures 1-1. Structure Smaller Than A Word 1-2. No Padding 1-3. Internal and Tail Padding 1-4. Bit-Field Ranges I. Low Level System Information Table of Contents 1. Machine Interface 2. Function Calling Sequence 3. Operating System Interface 4. Process Initialization 5. Coding Examples 6. C Stack Frame 7. Debug Information ------------------------------------------------------------------------------- Chapter 1. Machine Interface Processor Architecture The Architecture is specified by the following documents * Itanium ? Architecture Software Developer's Manual Volume 1: Application Architecture * Itanium ? Architecture Software Developer's Manual Volume 2: System Architecture * Itanium ? Architecture Software Developer's Manual Volume 3: Instruction Set Reference * IA-64 Processor Reference: Intel Itanium ? Processor Reference Manual for Software Development * Itanium ? Software Conventions & Runtime Architecture Guide * Intel Itanium ? Processor-specific Application Binary Interface Only the features of the processor instruction set may be assumed to be present. An application is responsible for determining 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. Only instructions which do not require elevated privileges may be used. Applications may not make system calls directly. The interfaces in the C library must be used instead. There are some features of the processor architecture that need not be supported by a conforming implementation. These are described in this chapter. A conforming application shall not rely on these features. 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 specfication does not provide any performance guarantees of a conforming system. A system conforming to this specification may be implemented in either hardware or software. This specification describes only LP64 (i.e. 32-bit integers, 64-bit longs and pointers) based implementations. Implementations may also provide ILP32 (32-bit integers, longs, and pointers), but conforming applications shall not rely on support for ILP32. See section 1.2 of the Intel Itanium ? Processor-specific Application Binary Interface for further information. ------------------------------------------------------------------------------- Data Representation See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 4. Within this specification, the term byte refers to an 8-bit object, the term halfword refers to a 16-bit object, the term word refers to a 32-bit object, the term doubleword refers to a 64-bit object, and the term quadword refers to a 128-bit object. Although the architecture also supports 120-bit addressable objects, this specification does not require LSB-conforming implementations to provide support for these objects. ------------------------------------------------------------------------------- Byte Ordering LSB-conforming applications shall use little-endian byte ordering. LSB-conforming implementations may support big-endian applications. ------------------------------------------------------------------------------- Fundamental Types Table 2-1 describes how fundemental C language data types shall be represented: Table 1-1. Scalar Types +-------------------------------------------------------------------------+ | Type | C |sizeof|Alignment (bytes)| Notes | |--------------+------------------+------+-----------------+--------------| | |char | | | | | |------------------| | | | | |signed char |1 |1 | | | |------------------| | | | | |unsigned char | | | | | |------------------+------+-----------------+--------------| | |short | | | | | |------------------| | | | | |signed short |2 |2 | | | |------------------| | | | | |unsigned short | | | | | |------------------+------+-----------------+--------------| | |int | | | | | |------------------| | | | |Integral |signed int |4 |4 | | | |------------------| | | | | |unsigned int | | | | | |------------------+------+-----------------+--------------| | |long | | | | | |------------------| | | | | |signed long |8 |8 | | | |------------------| | | | | |unsigned long | | | | | |------------------+------+-----------------+--------------| | |long long | | | | | |------------------| | | | | |signed long long |8 |8 |See Note Below| | |------------------| | | | | |unsigned long long| | | | |--------------+------------------+------+-----------------+--------------| | |any-type * | | | | |Pointer |------------------|8 |8 | | | |any-type (*)() | | | | |--------------+------------------+------+-----------------+--------------| | |float |4 |4 | | | |------------------+------+-----------------+--------------| |Floating-Point|double |8 |8 | | | |------------------+------+-----------------+--------------| | |long double |16 |16 | | +-------------------------------------------------------------------------+ Note: Support for the long long data type is dependent on support for ISO9899:1999 C language. This standard is not required for LSB-conformance, but this data type is important when developing applications for the architecture. The GNU Compiler Collection (gcc) includes support for long long of ISO9899:1999. A null pointer (for all types) shall have the value zero. ------------------------------------------------------------------------------- Aggregates and Unions Aggregates (structures and arrays) and unions assume the alignment of their most strictly aligned component. The size of any object, including aggregates and unions, shall always be a multiple of the object's alignment. An array uses the same alignment as its elements. Structure and union objects may require padding to meet size and element constraints. The contents of such padding is undefined. * An entire structure or union object shall be aligned on the same boundary as its most strictly aligned member. * Each member shall be assigned to the lowest available offset with the appropriate alignment. This may require internal padding, depending on the previous member. * A structure's size shall be increased, if necessary, to make it a multiple of the alignment. This may require tail padding, depending on the last member. A conforming application shall not read padding. Figure 1-1. Structure Smaller Than A Word +-------------------------+ | struct { | | char c; | | } | | | | | |-------------------------| |Byte aligned, sizeof is 1| +-------------------------+ +-------------+ |Offset|Byte 0| |------+------| |0 |c^0 | +-------------+ Figure 1-2. No Padding +--------------------------------+ | struct { | | char c; | | char d; | | short s; | | int i; | | long l; | | } | | | | | |--------------------------------| |Doubleword Aligned, sizeof is 16| +--------------------------------+ +--------------------------------------+ |Offset|Byte 3|Byte 2|Byte 1|Byte 0||||| |------+-------------+------+------++++| |0 |s^2 |d^1 |c^0 ||||| |------+---------------------------++++| |4 |i^0 ||||| |------+---------------------------++++| |8 | ||||| |------|l^0 |---| |12 | | | +--------------------------------------+ Figure 1-3. Internal and Tail Padding +--------------------------------+ | struct { | | char c; | | long l; | | int i; | | short s; | | } | | | | | |--------------------------------| |Doubleword Aligned, sizeof is 24| +--------------------------------+ +--------------------------------------+ |Offset|Byte 3|Byte 2|Byte 1|Byte 0||||| |------+--------------------+------++++| |0 |pad^1 |c^0 ||||| |------+---------------------------++++| |4 |pad^1 ||||| |------+---------------------------++++| |8 | ||||| |------|l^0 |---| |12 | | | |------+---------------------------+---| |16 |i^0 ||||| |------+---------------------------++++| |20 |pad^2 |s^0 ||||| +--------------------------------------+ ------------------------------------------------------------------------------- Bit Fields C struct and union definitions may have bit-fields, which define integral objects with a specified number of bits. Bit fields that are declared with neither signed nor unsigned specifier shall always be treated as unsigned. Bit fields obey the same size and alignment rules as other structure and union members, with the following additional properties: * Bit-fields are allocated from right to left (least to most significant). * A bit-field must entirely reside in a storage unit for its appropriate type. A bit field shall never cross its unit boundary. * Bit-fields may share a storage unit with other struct/union members, including members that are not bit fields. Such other struct/union members shall occupy different parts of the storage unit. * The type of unnamed bit-fields shall not affect the alignment of a structure or union, although individual bit-field member offsets shall obey the alignment constraints. Figure 1-4. Bit-Field Ranges +--------------------------------------+ |Bit-field Type| Width | Range | |--------------+-------+---------------| |signed char | |-2^-1 to 2^-1-1| |char | |0 to 2^-1 | |unsigned char |1 to 8 |0 to 2^-1 | | | | | | | | | |--------------+-------+---------------| |signed short | |-2^-1 to 2^-1-1| |short | |0 to 2^-1 | |unsigned short|1 to 16|0 to 2^-1 | | | | | | | | | |--------------+-------+---------------| |signed int | |-2^-1 to 2^-1-1| |int | |0 to 2^-1 | |unsigned int |1 to 32|0 to 2^-1 | | | | | | | | | |--------------+-------+---------------| |signed long | |-2^-1 to 2^-1-1| |long | |0 to 2^-1 | |unsigned long |1 to 64|0 to 2^-1 | | | | | | | | | +--------------------------------------+ ------------------------------------------------------------------------------- Chapter 2. Function Calling Sequence LSB-conforming applications shall use the procedure linkage and function calling sequence as defined in Chapter 8.4 of the Itanium ? Software Conventions & Runtime Architecture Guide. ------------------------------------------------------------------------------- CPU Registers The CPU general and other registers are as defined in the Itanium ? Architecture Software Developer's Manual Volume 1: Application Architecture Section 3.1. ------------------------------------------------------------------------------- Floating Point Registers The floating point registers are as defined in the Itanium ? Architecture Software Developer's Manual Volume 1: Application Architecture Section 3.1. ------------------------------------------------------------------------------- Stack Frame The stackframe layout is as described in the Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.4. ------------------------------------------------------------------------------- Arguments The procedure argument passing mechanism is as described in the Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.5. ------------------------------------------------------------------------------- Integral/Pointer See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.5. ------------------------------------------------------------------------------- Floating Point See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.5. ------------------------------------------------------------------------------- Struct and Union Point See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.5. ------------------------------------------------------------------------------- Variable Arguments See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.5.4. ------------------------------------------------------------------------------- Return Values See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.6. ------------------------------------------------------------------------------- Void Functions that return no value (void functions) are not required to put any particular value in any general register. ------------------------------------------------------------------------------- Integral/Pointer See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.6. ------------------------------------------------------------------------------- Floating Point See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.6. ------------------------------------------------------------------------------- Struct and Union See Itanium ? Software Conventions & Runtime Architecture Guide Chapter 8.6 (aggregate return values). Depending on the size (including any padding), aggregate data types may be passed in one or more general registers, or in memory. ------------------------------------------------------------------------------- Chapter 3. Operating System Interface LSB-conforming applications shall use the Operating System Interfaces as defined in Chapter 3 of the Intel Itanium ? Processor-specific Application Binary Interface. ------------------------------------------------------------------------------- Processor Execution Mode Applications must assume that they will execute in the least privileged user mode (i.e. level 3). Other privilege levels are reserved for the Operating System. ------------------------------------------------------------------------------- Exception Interface See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.1. ------------------------------------------------------------------------------- Hardware Exception Types See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.1. ------------------------------------------------------------------------------- Software Trap Types See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.1. ------------------------------------------------------------------------------- Debugging Support See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.4. ------------------------------------------------------------------------------- Process Startup See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.5. ------------------------------------------------------------------------------- Signal Delivery See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.2. ------------------------------------------------------------------------------- Signal Handler Interface See Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.3. ------------------------------------------------------------------------------- Chapter 4. Process Initialization LSB-conforming applications shall use the Process Startup as defined in Section 3.3.5 of the Intel Itanium ? Processor-specific Application Binary Interface. ------------------------------------------------------------------------------- Special Registers Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.5, defines required register initializations for process startup. ------------------------------------------------------------------------------- Process Stack (on entry) As defined in Intel Itanium ? Processor-specific Application Binary Interface, section 3.3.5, the return pointer register (rp) shall contain a valid return address, such that if the application program returns from the main entry routine, the implementation shall cause the application to exit normally, using the returned value as the exit status. Further, the unwind information for this "bottom of stack" routine in the implementation shall provide a mechanism for recognizing the bottom of the stack during a stack unwind. ------------------------------------------------------------------------------- Auxiliary Vector The auxiliary vector conveys information from the operating system to the application. Only the terminating null auxiliary vector entry is required, but if any other entries are present, they shall be interpreted as follows. This vector is an array of the following structures. typedef struct { long int a_type; /* Entry type */ union { long int a_val; /* Integer value */ void *a_ptr; /* Pointer value */ void (*a_fcn) (void); /* Function pointer value */ } a_un; } auxv_t; The application shall interpret the a_un value according to the a_type. Other auxiliary vector types are reserved. The a_type field shall contain one of the following values: AT_NULL The last entry in the array has type AT_NULL. The value in a_un is undefined. AT_IGNORE The value in a_un is undefined, and should be ignored. AT_EXECFD File descriptor of program AT_PHDR Program headers for program AT_PHENT Size of program header entry AT_PHNUM Number of program headers AT_PAGESZ System page size AT_BASE Base address of interpreter AT_FLAGS Flags AT_ENTRY Entry point of program AT_NOTELF Program is not ELF AT_UID Real uid AT_EUID Effective uid AT_GID Real gid AT_EGID Effective gid AT_CLKTCK Frequency of times() AT_PLATFORM String identifying platform. AT_HWCAP Machine dependent hints about processor capabilities. AT_FPUCW Used FPU control word AT_DCACHEBSIZE Data cache block size AT_ICACHEBSIZE Instruction cache block size AT_UCACHEBSIZE Unified cache block size Note: The auxiliary vector is intended for passing information from the operating system to the program interpreter. ------------------------------------------------------------------------------- Environment Although a pointer to the environment vector should be available as a third argument to the main entry point, conforming applications should use getenv to access the environment. (See ISO/IEC 9945:2003 Portable Operating System(POSIX) and The Single UNIX Specification(SUS) V3, Section exec). ------------------------------------------------------------------------------- Chapter 5. Coding Examples LSB-conforming applications may implement fundamental operations using the Coding Examples as shown below. Sample code sequences and coding conventions can be found in Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 9. ------------------------------------------------------------------------------- Code Model Overview/Architecture Constraints As defined in Intel Itanium ? Processor-specific Application Binary Interface, relocatable files, executable files, and shared object files that are supplied as part of an application must use Position Independent Code, as described in Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 12. ------------------------------------------------------------------------------- Position-Independent Function Prologue See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.4. ------------------------------------------------------------------------------- Data Objects See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.4, and Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 12.3. ------------------------------------------------------------------------------- Absolute Load & Store Conforming applications shall not use absolute addressing. ------------------------------------------------------------------------------- Position Relative Load & Store See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.4. ------------------------------------------------------------------------------- Function Calls See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.4. Four types of procedure call are defined in Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.3. Although special calling conventions are permitted, provided that the compiler and runtime library agree on these conventions, none are defined for this standard. Consequently, no application shall depend on a type of procedure call other than Direct Calls, Direct Dynamically Linked Calls, or Indirect Calls, as defined in Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.3. ------------------------------------------------------------------------------- Absolute Direct Function Call Conforming applications shall not use absolute addressing. ------------------------------------------------------------------------------- Absolute Indirect Function Call Conforming applications shall not use absolute addressing. ------------------------------------------------------------------------------- Position-Independent Direct Function Call See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.4.1. ------------------------------------------------------------------------------- Position-Independent Indirect Function Call See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.4.2. ------------------------------------------------------------------------------- Branching Branching is described in IA-64 Processor Reference: Intel Itanium ? Processor Reference Manual for Software Development, Chapter 4.5. ------------------------------------------------------------------------------- Branch Instruction See IA-64 Processor Reference: Intel Itanium ? Processor Reference Manual for Software Development, Chapter 4.5. ------------------------------------------------------------------------------- Absolute switch() code Conforming applications shall not use absolute addressing. ------------------------------------------------------------------------------- Position-Independent switch() code Where there are several possible targets for a branch, the compiler may use a number of different code generation strategies. See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 9.1.7. ------------------------------------------------------------------------------- Chapter 6. C Stack Frame Variable Argument List See Itanium ? Software Conventions & Runtime Architecture Guide, Chapter 8.5.2, and 8.5.4. ------------------------------------------------------------------------------- Dynamic Allocation of Stack Space The C library alloca function should be used to dynamically allocate stack space. ------------------------------------------------------------------------------- Chapter 7. Debug Information The LSB does not currently specify the format of Debug information. II. Object Format LSB-conforming implementations shall support an object file , called Executable and Linking Format (ELF) as defined by the System V Application Binary Interface, Edition 4.1, Intel Itanium ? Processor-specific Application Binary Interface and as supplemented by the Linux Standard Base Specification and this document. Table of Contents 8. ELF Header 9. Sections 10. Symbol Table 11. Relocation ------------------------------------------------------------------------------- Chapter 8. ELF Header Machine Information LSB-conforming applications shall use the Machine Information as defined in Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4. Implementations shall support the LP64 model. It is unspecified whether or not the ILP32 model shall also be supported. ------------------------------------------------------------------------------- File Class For LP64 relocatable objects, the file class value in e_ident[EI_CLASS] may be either ELFCLASS32 or ELFCLASS64, and a conforming linker must be able to process either or both classes. ------------------------------------------------------------------------------- Data Encoding Implementations shall support 2's complement, little endian data encoding. The data encoding value in e_ident[EI_DATA] shall contain the value ELFDATA2LSB. ------------------------------------------------------------------------------- OS Identification The OS Identification field e_ident[EI_OSABI] shall contain the value ELFOSABI_LINUX. ------------------------------------------------------------------------------- Processor Identification The processor identification value held in e_machine shall contain the value EM_IA_64. ------------------------------------------------------------------------------- Processor Specific Flags The flags field e_flags shall be as described in Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.1.1.6. The following additional processor-specific flags are defined: Table 8-1. Additional Processor-Specific Flags +------------------------------------------+ | Name | Value | |-------------------------------+----------| |EF_IA_64_LINUX_EXECUTABLE_STACK|0x00000001| +------------------------------------------+ EF_IA_64_LINUX_EXECUTABLE_STACK The stack and heap sections are executable. If this flag is not set, code can not be executed from the stack or heap. ------------------------------------------------------------------------------- Chapter 9. Sections The architecture defines two processor-specific section types, as described in Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4. ------------------------------------------------------------------------------- Special Sections The following sections are defined in the Intel Itanium ? Processor-specific Application Binary Interface. Table 9-1. ELF Special Sections +-----------------------------------------------------------------------+ | Name | Type | Attributes | |------------------+----------------+-----------------------------------| |.got |SHT_PROGBITS |SHF_ALLOC+SHF_WRITE+SHF_IA_64_SHORT| |------------------+----------------+-----------------------------------| |.IA_64.archext |SHT_IA_64_EXT |0 | |------------------+----------------+-----------------------------------| |.IA_64.pltoff |SHT_PROGBITS |SHF_ALLOC+SHF_WRITE+SHF_IA_64_SHORT| |------------------+----------------+-----------------------------------| |.IA_64.unwind |SHT_IA_64_UNWIND|SHF_ALLOC+SHF_LINK_ORDER | |------------------+----------------+-----------------------------------| |.IA_64.unwind_info|SHT_PROGBITS |SHF_ALLOC | |------------------+----------------+-----------------------------------| |.plt |SHT_PROGBITS |SHF_ALLOC+SHF_EXECINSTR | |------------------+----------------+-----------------------------------| |.sbss |SHT_NOBITS |SHF_ALLOC+SHF_WRITE | |------------------+----------------+-----------------------------------| |.sdata |SHT_PROGBITS |SHF_ALLOC+SHF_WRITE+SHF_IA_64_SHORT| |------------------+----------------+-----------------------------------| |.sdata1 |SHT_PROGBITS |SHF_ALLOC+SHF_WRITE+SHF_IA_64_SHORT| +-----------------------------------------------------------------------+ .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. .IA_64.archext This section holds product-specific extension bits. The link editor will perform a logical "or" of the extension bits of each object when creating an executable so that it creates only a single .IA_64.archext section in the executable. .IA_64.pltoff This section holds local function descriptor entries. .IA_64.unwind This section holds the unwind function table. The contents are described in the Intel (r) Itanium (tm) Processor Specific ABI. .IA_64.unwind_info This section holds stack unwind and and exception handling information. The exception handling information is programming language specific, and is unspecified. .plt This section holds the Procedure Linkage Table. .sbss This section holds uninitialized data that contribute to the program''s memory image. Data objects contained in this section are recommended to be eight bytes or less in size. The system initializes the data with zeroes when the program begins to run. The section occupies no file space, as indicated by the section type SHT_NOBITS. The .sbss section is placed so it may be accessed using short direct addressing (22 bit offset from gp). .sdata This section and the .sdata1 section hold initialized data that contribute to the program''s memory image. Data objects contained in this section are recommended to be eight bytes or less in size. The .sdata and .sdata1 sections are placed so they may be accessed using short direct addressing (22 bit offset from gp). .sdata1 See .sdata. ------------------------------------------------------------------------------- Linux Special Sections The following Linux IA-64 specific sections are defined here. Table 9-2. Additional Special Sections +------------------------------------------+ | Name | Type |Attributes| |------------------+------------+----------| |.opd |SHT_PROGBITS|SHF_ALLOC | |------------------+------------+----------| |.rela.dyn |SHT_RELA |SHF_ALLOC | |------------------+------------+----------| |.rela.IA_64.pltoff|SHT_RELA |SHF_ALLOC | +------------------------------------------+ .opd This section holds function descriptors .rela.dyn This section holds relocation information, as described in `Relocation'. These relocations are applied to the .dyn section. .rela.IA_64.pltoff This section holds relocation information, as described in `Relocation'. These relocations are applied to the .IA_64.pltoff section. ------------------------------------------------------------------------------- Section Types Section Types are described in the Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.2. LSB conforming implementations are not required to use any sections in the range from SHT_IA_64_LOPSREG to SHT_IA_64_HIPSREG. Additionally, LSB conforming implementations are not required to support the SHT_IA_64_PRIORITY_INIT section, beyond the gABI requirements for the handling of unrecognized section types, linking them into a contiguous section in the object file created by the static linker. ------------------------------------------------------------------------------- Section Attribute Flags See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.2.2. ------------------------------------------------------------------------------- Special Section Types See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.2.3. ------------------------------------------------------------------------------- Chapter 10. Symbol Table If an executable file contains a reference to a function defined in one of its associated shared objects, the symbol table section for that file shall contain an entry for that symbol. The st_shndx member of that symbol table entry contains SHN_UNDEF. This signals to the dynamic linker that the symbol definition for that function is not contained in the executable file itself. If that symbol has been allocated a procedure linkage table entry in the executable file, and the st_value member for that symbol table entry is non-zero, the value shall contain the virtual address of the first instruction of that procedure linkage table entry. Otherwise, the st_value member contains zero. This procedure linkage table entry address is used by the dynamic linker in resolving references to the address of the function. Note: Need to add something here about st_info and st_other ... ------------------------------------------------------------------------------- Chapter 11. Relocation LSB-conforming applications shall use Relocations as defined in Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.3. ------------------------------------------------------------------------------- Relocation Types See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 4.3. III. Program Loading and Dynamic Linking LSB-conforming implementations shall support the object file information and system actions that create running programs as specified in the System V Application Binary Interface, Edition 4.1, Intel Itanium ? Processor-specific Application Binary Interface and as supplemented by the Linux Standard Base Specification and this document. Table of Contents 12. Program Header 13. Program Loading 14. Dynamic Linking ------------------------------------------------------------------------------- Chapter 12. Program Header The program header shall be as defined in the Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5. ------------------------------------------------------------------------------- Types See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.1. ------------------------------------------------------------------------------- Flags See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.1. ------------------------------------------------------------------------------- Chapter 13. Program Loading See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.2. ------------------------------------------------------------------------------- Chapter 14. Dynamic Linking See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3. ------------------------------------------------------------------------------- Dynamic Entries ELF Dynamic Entries The following dynamic entries are defined in the Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.2. DT_PLTGOT This entry's d_ptr member gives the address of the first byte in the procedure linkage table ------------------------------------------------------------------------------- Additional Dynamic Entries The following dynamic entries are defined here. DT_RELACOUNT The number of relative relocations in .rela.dyn ------------------------------------------------------------------------------- Global Offset Table See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.4. ------------------------------------------------------------------------------- Shared Object Dependencies See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.3. ------------------------------------------------------------------------------- Function Addresses See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.5. ------------------------------------------------------------------------------- Procedure Linkage Table See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.6. ------------------------------------------------------------------------------- Initialization and Termination Functions See Intel Itanium ? Processor-specific Application Binary Interface, Chapter 5.3.7. Linux Standard Base Specification ------------------------------------------------------------------------------- Table of Contents I. Base Libraries 1. Libraries Program Interpreter/Dynamic Linker Interfaces for libc Data Definitions for libc Interfaces for libm Interfaces for libpthread Interfaces for libgcc_s Interface Definitions for libgcc_s Interfaces for libdl Interfaces for libcrypt II. Utility Libraries 2. Libraries Interfaces for libz Interfaces for libncurses Interfaces for libutil A. Alphabetical Listing of Interfaces libgcc_s List of Tables 1-1. libc Definition 1-2. libc - RPC Function Interfaces 1-3. libc - System Calls Function Interfaces 1-4. libc - Standard I/O Function Interfaces 1-5. libc - Standard I/O Data Interfaces 1-6. libc - Signal Handling Function Interfaces 1-7. libc - Signal Handling Data Interfaces 1-8. libc - Localization Functions Function Interfaces 1-9. libc - Localization Functions Data Interfaces 1-10. libc - Socket Interface Function Interfaces 1-11. libc - Socket Interface Deprecated Function Interfaces 1-12. libc - Wide Characters Function Interfaces 1-13. libc - String Functions Function Interfaces 1-14. libc - IPC Functions Function Interfaces 1-15. libc - Regular Expressions Function Interfaces 1-16. libc - Regular Expressions Deprecated Function Interfaces 1-17. libc - Regular Expressions Deprecated Data Interfaces 1-18. libc - Character Type Functions Function Interfaces 1-19. libc - Time Manipulation Function Interfaces 1-20. libc - Time Manipulation Deprecated Function Interfaces 1-21. libc - Time Manipulation Data Interfaces 1-22. libc - Terminal Interface Functions Function Interfaces 1-23. libc - System Database Interface Function Interfaces 1-24. libc - Language Support Function Interfaces 1-25. libc - Large File Support Function Interfaces 1-26. libc - Standard Library Function Interfaces 1-27. libc - Standard Library Data Interfaces 1-28. libm Definition 1-29. libm - Math Function Interfaces 1-30. libm - Math Data Interfaces 1-31. libpthread Definition 1-32. libpthread - Posix Threads Function Interfaces 1-33. libgcc_s Definition 1-34. libgcc_s - Unwind Library Function Interfaces 1-35. libdl Definition 1-36. libdl - Dynamic Loader Function Interfaces 1-37. libcrypt Definition 1-38. libcrypt - Encryption Function Interfaces 2-1. libz Definition 2-2. libncurses Definition 2-3. libutil Definition 2-4. libutil - Utility Functions Function Interfaces A-1. libgcc_s Function Interfaces I. Base Libraries Table of Contents 1. Libraries ------------------------------------------------------------------------------- Chapter 1. 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 Itanium? platform are defined here. This section should be used in conjunction with the corresponding section in the Linux Standard Base Specification. ------------------------------------------------------------------------------- Program Interpreter/Dynamic Linker The LSB specifies the Program Interpreter to be /lib/ld-lsb-ia64.so.2. ------------------------------------------------------------------------------- Interfaces for libc Table 1-1 defines the library name and shared object name for the libc library Table 1-1. libc Definition +---------------------+ |Library:|libc | |--------+------------| |SONAME: |libc.so.6.1 | +---------------------+ The behavior of the interfaces in this library is specified by the following specifications: Large File Support Linux Standard Base CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 System V Interface Definition, Issue 3 (ISBN 0201566524) System V Interface Definition,Fourth Edition ------------------------------------------------------------------------------- RPC ------------------------------------------------------------------------------- Interfaces for RPC An LSB conforming implementation shall provide the architecture specific functions for RPC specified in Table 1-2, with the full functionality as described in the referenced underlying specification. Table 1-2. libc - RPC Function Interfaces +----------------------------------------------------------------------------------------+ |authnone_create |pmap_unset |svcerr_weakauth |xdr_float |xdr_u_char | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_create |setdomainname |svctcp_create |xdr_free |xdr_u_int | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[2] | |------------------+----------------+------------------+------------------+--------------| |clnt_pcreateerror |svc_getreqset |svcudp_create |xdr_int(GLIBC_2.2)|xdr_u_long | |(GLIBC_2.2) [1] |(GLIBC_2.2) [3] |(GLIBC_2.2) [2] |[3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_perrno |svc_register |xdr_accepted_reply|xdr_long |xdr_u_short | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_perror |svc_run |xdr_array |xdr_opaque |xdr_union | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_spcreateerror|svc_sendreply |xdr_bool |xdr_opaque_auth |xdr_vector | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_sperrno |svcerr_auth |xdr_bytes |xdr_pointer |xdr_void | |(GLIBC_2.2) [1] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |clnt_sperror |svcerr_decode |xdr_callhdr |xdr_reference |xdr_wrapstring| |(GLIBC_2.2) [1] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |getdomainname |svcerr_noproc |xdr_callmsg |xdr_rejected_reply|xdrmem_create | |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |key_decryptsession|svcerr_noprog |xdr_char |xdr_replymsg |xdrrec_create | |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |pmap_getport |svcerr_progvers |xdr_double |xdr_short |xdrrec_eof | |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) | | | | | |[3] | |------------------+----------------+------------------+------------------+--------------| |pmap_set |svcerr_systemerr|xdr_enum |xdr_string | | |(GLIBC_2.2) [2] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] |(GLIBC_2.2) [3] | | +----------------------------------------------------------------------------------------+ Referenced Specification(s) [1]. System V Interface Definition,Fourth Edition [2]. Linux Standard Base [3]. System V Interface Definition, Issue 3 (ISBN 0201566524) ------------------------------------------------------------------------------- System Calls ------------------------------------------------------------------------------- Interfaces for System Calls An LSB conforming implementation shall provide the architecture specific functions for System Calls specified in Table 1-3, with the full functionality as described in the referenced underlying specification. Table 1-3. libc - System Calls Function Interfaces +-----------------------------------------------------------------------------+ |__fxstat |fchmod |getwd | |setrlimit | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |read(GLIBC_2.2) [2] |(GLIBC_2.2) | |[1] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |__getpgid |fchown |initgroups | |setrlimit64 | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |readdir(GLIBC_2.2) [2]|(GLIBC_2.2) | |[1] |[2] |[1] | |[3] | |------------+-------------+-------------+----------------------+-------------| |__lxstat |fcntl |ioctl |readdir_r(GLIBC_2.2) |setsid | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[1] |[1] |[1] | |[2] | |------------+-------------+-------------+----------------------+-------------| |__xmknod |fdatasync |kill |readlink(GLIBC_2.2) |setuid | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[1] |[2] |[1] | |[2] | |------------+-------------+-------------+----------------------+-------------| |__xstat |flock |killpg | |sleep | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |readv(GLIBC_2.2) [2] |(GLIBC_2.2) | |[1] |[1] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |access |fork |lchown | |statvfs | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |rename(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |acct |fstatvfs |link | |stime | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |rmdir(GLIBC_2.2) [2] |(GLIBC_2.2) | |[1] |[2] |[2] | |[1] | |------------+-------------+-------------+----------------------+-------------| |alarm |fsync |lockf | |symlink | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |sbrk(GLIBC_2.2) [4] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |brk |ftime |lseek |sched_get_priority_max|sync | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[4] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |chdir |ftruncate |mkdir |sched_get_priority_min|sysconf | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |chmod |getcontext |mkfifo |sched_getparam |time | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |chown |getegid |mlock |sched_getscheduler |times | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |chroot |geteuid |mlockall |sched_rr_get_interval |truncate | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[4] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |clock |getgid |mmap |sched_setparam |ulimit | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |close |getgroups |mprotect |sched_setscheduler |umask | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |closedir |getitimer |msync |sched_yield(GLIBC_2.2)|uname | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |creat |getloadavg |munlock | |unlink | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |select(GLIBC_2.2) [2] |(GLIBC_2.2) | |[1] |[1] |[2] | |[1] | |------------+-------------+-------------+----------------------+-------------| |dup |getpagesize |munlockall |setcontext(GLIBC_2.2) |utime | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[2] |[4] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |dup2 |getpgid |munmap | |utimes | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |setegid(GLIBC_2.2) [2]|(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |execl |getpgrp |nanosleep | |vfork | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |seteuid(GLIBC_2.2) [2]|(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |execle |getpid |nice | |wait | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |setgid(GLIBC_2.2) [2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |execlp |getppid |open |setitimer(GLIBC_2.2) |wait3 | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[2] |[2] |[1] | |[1] | |------------+-------------+-------------+----------------------+-------------| |execv |getpriority |opendir | |wait4 | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |setpgid(GLIBC_2.2) [2]|(GLIBC_2.2) | |[2] |[2] |[2] | |[1] | |------------+-------------+-------------+----------------------+-------------| |execve |getrlimit |pathconf | |waitpid | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |setpgrp(GLIBC_2.2) [2]|(GLIBC_2.2) | |[2] |[2] |[2] | |[1] | |------------+-------------+-------------+----------------------+-------------| |execvp |getrusage |pause |setpriority(GLIBC_2.2)|write | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |exit |getsid |pipe |setregid(GLIBC_2.2) |writev | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) | |[2] |[2] |[2] | |[2] | |------------+-------------+-------------+----------------------+-------------| |fchdir |getuid |poll |setreuid(GLIBC_2.2) | | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |[2] | | |[2] |[2] |[2] | | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [3]. Large File Support [4]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) ------------------------------------------------------------------------------- Standard I/O ------------------------------------------------------------------------------- Interfaces for Standard I/O An LSB conforming implementation shall provide the architecture specific functions for Standard I/O specified in Table 1-4, with the full functionality as described in the referenced underlying specification. Table 1-4. libc - Standard I/O Function Interfaces +-----------------------------------------------------------------------------+ |_IO_feof |fgetpos |fsetpos |putchar |sscanf | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |_IO_getc |fgets |ftell(GLIBC_2.2)|putchar_unlocked|telldir | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|[2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |_IO_putc |fgetwc_unlocked|ftello |puts(GLIBC_2.2) |tempnam | |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]|(GLIBC_2.2) [2] |[2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |_IO_puts |fileno |fwrite |putw(GLIBC_2.2) |ungetc | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |[3] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |asprintf |flockfile |getc(GLIBC_2.2) |remove |vasprintf | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|[2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[1] | |---------------+---------------+----------------+----------------+-----------| |clearerr |fopen |getc_unlocked |rewind |vdprintf | |(GLIBC_2.2) [2]|(GLIBC_2.2) [1]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[1] | |---------------+---------------+----------------+----------------+-----------| |ctermid |fprintf |getchar |rewinddir |vfprintf | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |fclose |fputc |getchar_unlocked|scanf(GLIBC_2.2)|vprintf | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |[2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |fdopen |fputs |getw(GLIBC_2.2) |seekdir |vsnprintf | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|[3] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |feof(GLIBC_2.2)|fread |pclose |setbuf |vsprintf | |[2] |(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2)| | | | | |[2] | |---------------+---------------+----------------+----------------+-----------| |ferror |freopen |popen(GLIBC_2.2)|setbuffer | | |(GLIBC_2.2) [2]|(GLIBC_2.2) [1]|[2] |(GLIBC_2.2) [1] | | |---------------+---------------+----------------+----------------+-----------| |fflush |fscanf |printf |setvbuf | | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | | |---------------+---------------+----------------+----------------+-----------| |fflush_unlocked|fseek |putc(GLIBC_2.2) |snprintf | | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|[2] |(GLIBC_2.2) [2] | | |---------------+---------------+----------------+----------------+-----------| |fgetc |fseeko |putc_unlocked |sprintf | | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [3]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) An LSB conforming implementation shall provide the architecture specific data interfaces for Standard I/O specified in Table 1-5, with the full functionality as described in the referenced underlying specification. Table 1-5. libc - Standard I/O Data Interfaces +--------------------------------------------------------------------+ |stderr(GLIBC_2.2) [1]|stdin(GLIBC_2.2) [1]|stdout(GLIBC_2.2) [1]| | | +--------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Signal Handling ------------------------------------------------------------------------------- Interfaces for Signal Handling An LSB conforming implementation shall provide the architecture specific functions for Signal Handling specified in Table 1-6, with the full functionality as described in the referenced underlying specification. Table 1-6. libc - Signal Handling Function Interfaces +-----------------------------------------------------------------------------+ |__libc_current_sigrtmax|sigaddset |sighold |sigpause |sigsuspend | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |-----------------------+------------+-------------+------------+-------------| |__libc_current_sigrtmin|sigaltstack |sigignore |sigpending |sigtimedwait | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |-----------------------+------------+-------------+------------+-------------| |__sigsetjmp(GLIBC_2.2) |sigandset |siginterrupt |sigprocmask |sigwait | |[1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[2] |[2] |[2] | |-----------------------+------------+-------------+------------+-------------| |__sysv_signal |sigblock |sigisemptyset|sigqueue |sigwaitinfo | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[1] |[2] |[2] | |-----------------------+------------+-------------+------------+-------------| |bsd_signal(GLIBC_2.2) |sigdelset |sigismember |sigrelse | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |-----------------------+------------+-------------+------------+-------------| | |sigemptyset |siglongjmp |sigreturn | | |psignal(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[1] | | |-----------------------+------------+-------------+------------+-------------| | |sigfillset |signal |sigset | | |raise(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |-----------------------+------------+-------------+------------+-------------| |sigaction(GLIBC_2.2) |siggetmask |sigorset |sigstack | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[1] |[1] |[3] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [3]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) An LSB conforming implementation shall provide the architecture specific data interfaces for Signal Handling specified in Table 1-7, with the full functionality as described in the referenced underlying specification. Table 1-7. libc - Signal Handling Data Interfaces +-------------------------------------+ |_sys_siglist(GLIBC_2.3.3) [1]| | | | | +-------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Localization Functions ------------------------------------------------------------------------------- Interfaces for Localization Functions An LSB conforming implementation shall provide the architecture specific functions for Localization Functions specified in Table 1-8, with the full functionality as described in the referenced underlying specification. Table 1-8. libc - Localization Functions Function Interfaces +-----------------------------------------------------------------------------+ |bind_textdomain_codeset|catopen |dngettext |iconv_open |setlocale | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |-----------------------+------------+-------------+-------------+------------| |bindtextdomain |dcgettext |gettext |localeconv |textdomain | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[1] |[2] |[1] | |-----------------------+------------+-------------+-------------+------------| | |dcngettext |iconv |ngettext | | |catclose(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[1] |[2] |[1] | | |-----------------------+------------+-------------+-------------+------------| | |dgettext |iconv_close |nl_langinfo | | |catgets(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[1] |[2] |[2] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 An LSB conforming implementation shall provide the architecture specific data interfaces for Localization Functions specified in Table 1-9, with the full functionality as described in the referenced underlying specification. Table 1-9. libc - Localization Functions Data Interfaces +---------------------------------------+ |_nl_msg_cat_cntr(GLIBC_2.2) [1]| | | | | +---------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Socket Interface ------------------------------------------------------------------------------- Interfaces for Socket Interface An LSB conforming implementation shall provide the architecture specific functions for Socket Interface specified in Table 1-10, with the full functionality as described in the referenced underlying specification. Table 1-10. libc - Socket Interface Function Interfaces +-----------------------------------------------------------------------------+ |__h_errno_location|gethostid |listen |sendmsg |socketpair | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+-------------+--------------+--------------| |accept(GLIBC_2.2) |gethostname |recv |sendto | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |------------------+--------------+-------------+--------------+--------------| |bind(GLIBC_2.2) |getpeername |recvfrom |setsockopt | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[1] | | |------------------+--------------+-------------+--------------+--------------| |bindresvport |getsockname |recvmsg |shutdown | | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |------------------+--------------+-------------+--------------+--------------| |connect(GLIBC_2.2)|getsockopt |send |socket | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 An LSB conforming implementation shall provide the architecture specific deprecated functions for Socket Interface specified in Table 1-11, with the full 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 1-11. libc - Socket Interface Deprecated Function Interfaces +--------------------------------------+ |gethostbyname_r(GLIBC_2.2) [1]| | | | | +--------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Wide Characters ------------------------------------------------------------------------------- Interfaces for Wide Characters An LSB conforming implementation shall provide the architecture specific functions for Wide Characters specified in Table 1-12, with the full functionality as described in the referenced underlying specification. Table 1-12. libc - Wide Characters Function Interfaces +-----------------------------------------------------------------------------+ |__wcstod_internal |mbsinit |vwscanf |wcsnlen |wcstoumax | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[2] | |------------------+--------------+--------------+--------------+-------------| |__wcstof_internal |mbsnrtowcs |wcpcpy |wcsnrtombs |wcstouq | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[1] |[1] |[1] | |------------------+--------------+--------------+--------------+-------------| |__wcstol_internal |mbsrtowcs |wcpncpy |wcspbrk |wcswcs | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |__wcstold_internal|mbstowcs |wcrtomb |wcsrchr |wcswidth | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |__wcstoul_internal|mbtowc |wcscasecmp |wcsrtombs |wcsxfrm | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |btowc(GLIBC_2.2) |putwc |wcscat |wcsspn |wctob | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fgetwc(GLIBC_2.2) |putwchar |wcschr |wcsstr |wctomb | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fgetws(GLIBC_2.2) |swprintf |wcscmp |wcstod |wctrans | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fputwc(GLIBC_2.2) |swscanf |wcscoll |wcstof |wctype | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fputws(GLIBC_2.2) |towctrans |wcscpy |wcstoimax |wcwidth | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fwide(GLIBC_2.2) |towlower |wcscspn |wcstok |wmemchr | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fwprintf |towupper |wcsdup |wcstol |wmemcmp | |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |fwscanf(GLIBC_2.2)|ungetwc |wcsftime |wcstold |wmemcpy | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |getwc(GLIBC_2.2) |vfwprintf |wcslen |wcstoll |wmemmove | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |getwchar |vfwscanf |wcsncasecmp |wcstombs |wmemset | |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |mblen(GLIBC_2.2) |vswprintf |wcsncat |wcstoq |wprintf | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[2] | |------------------+--------------+--------------+--------------+-------------| |mbrlen(GLIBC_2.2) |vswscanf |wcsncmp |wcstoul |wscanf | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |------------------+--------------+--------------+--------------+-------------| |mbrtowc(GLIBC_2.2)|vwprintf |wcsncpy |wcstoull | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- String Functions ------------------------------------------------------------------------------- Interfaces for String Functions An LSB conforming implementation shall provide the architecture specific functions for String Functions specified in Table 1-13, with the full functionality as described in the referenced underlying specification. Table 1-13. libc - String Functions Function Interfaces +----------------------------------------------------------------------------+ |__mempcpy |bzero |strcasestr |strncasecmp |strtoimax | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[2] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__rawmemchr |ffs |strcat |strncat |strtok | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__stpcpy(GLIBC_2.2)|index |strchr |strncmp |strtok_r | |[1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[1] | |-------------------+-------------+-------------+--------------+-------------| |__strdup(GLIBC_2.2)|memccpy |strcmp |strncpy |strtold | |[1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__strtod_internal |memchr |strcoll |strndup |strtoll | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__strtof_internal |memcmp |strcpy |strnlen |strtoq | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[1] | |-------------------+-------------+-------------+--------------+-------------| |__strtok_r |memcpy |strcspn |strpbrk |strtoull | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__strtol_internal |memmove |strdup |strptime |strtoumax | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__strtold_internal |memrchr |strerror |strrchr |strtouq | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[2] |[2] |[1] | |-------------------+-------------+-------------+--------------+-------------| |__strtoll_internal |memset |strerror_r |strsep |strverscmp | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[1] |[1] |[1] | |-------------------+-------------+-------------+--------------+-------------| |__strtoul_internal |rindex |strfmon |strsignal |strxfrm | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[1] |[2] | |-------------------+-------------+-------------+--------------+-------------| |__strtoull_internal|stpcpy |strfry |strspn |swab | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[1] |[1] |[2] |[2] | |-------------------+-------------+-------------+--------------+-------------| | |stpncpy |strftime |strstr | | |bcmp(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[1] |[2] |[2] | | |-------------------+-------------+-------------+--------------+-------------| |bcopy(GLIBC_2.2) |strcasecmp |strlen |strtof | | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | +----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- IPC Functions ------------------------------------------------------------------------------- Interfaces for IPC Functions An LSB conforming implementation shall provide the architecture specific functions for IPC Functions specified in Table 1-14, with the full functionality as described in the referenced underlying specification. Table 1-14. libc - IPC Functions Function Interfaces +-----------------------------------------------------------------------------+ |ftok(GLIBC_2.2) |msgrcv(GLIBC_2.2) |semget(GLIBC_2.2) |shmctl(GLIBC_2.2) | | |[1] |[1] |[1] |[1] | | |------------------+------------------+------------------+------------------+-| |msgctl(GLIBC_2.2) |msgsnd(GLIBC_2.2) |semop(GLIBC_2.2) |shmdt(GLIBC_2.2) | | |[1] |[1] |[1] |[1] | | |------------------+------------------+------------------+------------------+-| |msgget(GLIBC_2.2) |semctl(GLIBC_2.2) |shmat(GLIBC_2.2) |shmget(GLIBC_2.2) | | |[1] |[1] |[1] |[1] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Regular Expressions ------------------------------------------------------------------------------- Interfaces for Regular Expressions An LSB conforming implementation shall provide the architecture specific functions for Regular Expressions specified in Table 1-15, with the full functionality as described in the referenced underlying specification. Table 1-15. libc - Regular Expressions Function Interfaces +-----------------------------------------------------------------------------+ |regcomp(GLIBC_2.2)|regerror |regexec(GLIBC_2.2)|regfree(GLIBC_2.2)| | |[1] |(GLIBC_2.2) [1] |[1] |[1] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 An LSB conforming implementation shall provide the architecture specific deprecated functions for Regular Expressions specified in Table 1-16, with the full 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 1-16. libc - Regular Expressions Deprecated Function Interfaces +------------------------------------------------------------------------------+ |advance(GLIBC_2.2) |re_comp(GLIBC_2.2) |re_exec(GLIBC_2.2) |step(GLIBC_2.2) | | |[1] |[1] |[1] |[1] | | +------------------------------------------------------------------------------+ Referenced Specification(s) [1]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) An LSB conforming implementation shall provide the architecture specific deprecated data interfaces for Regular Expressions specified in Table 1-17, with the full 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 1-17. libc - Regular Expressions Deprecated Data Interfaces +---------------------------------------------------------------+ |loc1(GLIBC_2.2) [1]|loc2(GLIBC_2.2) [1]|locs(GLIBC_2.2) [1]| | | +---------------------------------------------------------------+ Referenced Specification(s) [1]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) ------------------------------------------------------------------------------- Character Type Functions ------------------------------------------------------------------------------- Interfaces for Character Type Functions An LSB conforming implementation shall provide the architecture specific functions for Character Type Functions specified in Table 1-18, with the full functionality as described in the referenced underlying specification. Table 1-18. libc - Character Type Functions Function Interfaces +-----------------------------------------------------------------------------+ |__ctype_get_mb_cur_max|isdigit |iswalnum |iswlower |toascii | |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |----------------------+------------+-------------+--------------+------------| |_tolower(GLIBC_2.2) |isgraph |iswalpha |iswprint |tolower | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |----------------------+------------+-------------+--------------+------------| |_toupper(GLIBC_2.2) |islower |iswblank |iswpunct |toupper | |[2] |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | |[2] |[2] |[2] |[2] | |----------------------+------------+-------------+--------------+------------| | |isprint |iswcntrl |iswspace | | |isalnum(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |----------------------+------------+-------------+--------------+------------| | |ispunct |iswctype |iswupper | | |isalpha(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[1] |[2] | | |----------------------+------------+-------------+--------------+------------| | |isspace |iswdigit |iswxdigit | | |isascii(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | |----------------------+------------+-------------+--------------+------------| | |isupper |iswgraph |isxdigit | | |iscntrl(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) | | | |[2] |[2] |[2] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Time Manipulation ------------------------------------------------------------------------------- Interfaces for Time Manipulation An LSB conforming implementation shall provide the architecture specific functions for Time Manipulation specified in Table 1-19, with the full functionality as described in the referenced underlying specification. Table 1-19. libc - Time Manipulation Function Interfaces +-----------------------------------------------------------------------------+ |adjtime |ctime |gmtime |localtime_r |ualarm | |(GLIBC_2.2) [1]|(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2) [2] |(GLIBC_2.2) | | |[2] | | |[2] | |---------------+--------------+---------------+----------------+-------------| |asctime |ctime_r |gmtime_r |mktime | | |(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2) [2] | | | |[2] | | | | |---------------+--------------+---------------+----------------+-------------| |asctime_r |difftime |localtime |tzset(GLIBC_2.2)| | |(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]|[2] | | | |[2] | | | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 An LSB conforming implementation shall provide the architecture specific deprecated functions for Time Manipulation specified in Table 1-20, with the full 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 1-20. libc - Time Manipulation Deprecated Function Interfaces +--------------------------------+ |adjtimex(GLIBC_2.2) [1] | | | | | +--------------------------------+ Referenced Specification(s) [1]. Linux Standard Base An LSB conforming implementation shall provide the architecture specific data interfaces for Time Manipulation specified in Table 1-21, with the full functionality as described in the referenced underlying specification. Table 1-21. libc - Time Manipulation Data Interfaces +-----------------------------------------------------------------------------+ |__daylight(GLIBC_2.2) [1]|__tzname(GLIBC_2.2) [1]|timezone(GLIBC_2.2) [2]| | | |-------------------------+-----------------------+-----------------------+-+-| |__timezone(GLIBC_2.2) [1]|daylight(GLIBC_2.2) [2]|tzname(GLIBC_2.2) [2] | | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Terminal Interface Functions ------------------------------------------------------------------------------- Interfaces for Terminal Interface Functions An LSB conforming implementation shall provide the architecture specific functions for Terminal Interface Functions specified in Table 1-22, with the full functionality as described in the referenced underlying specification. Table 1-22. libc - Terminal Interface Functions Function Interfaces +----------------------------------------------------------------------------+ |cfgetispeed |cfsetispeed |tcdrain |tcgetattr |tcsendbreak | |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1]| | | |[1] |[1] | | |---------------+---------------+-------------+--------------+---------------| |cfgetospeed |cfsetospeed |tcflow |tcgetpgrp |tcsetattr | |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1]| | | |[1] |[1] | | |---------------+---------------+-------------+--------------+---------------| |cfmakeraw |cfsetspeed |tcflush |tcgetsid |tcsetpgrp | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1]| | | |[1] |[1] | | +----------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [2]. Linux Standard Base ------------------------------------------------------------------------------- System Database Interface ------------------------------------------------------------------------------- Interfaces for System Database Interface An LSB conforming implementation shall provide the architecture specific functions for System Database Interface specified in Table 1-23, with the full functionality as described in the referenced underlying specification. Table 1-23. libc - System Database Interface Function Interfaces +------------------------------------------------------------------------------+ |endgrent |getgrgid |getprotobynumber|getservbyport |setgrent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[1] | | | |[1] | |--------------+---------------+----------------+---------------+--------------| |endnetent |getgrgid_r |getprotoent |getservent |setgroups | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[1] | | | |[2] | |--------------+---------------+----------------+---------------+--------------| |endprotoent |getgrnam |getpwent |getutent |setnetent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [2]|(GLIBC_2.2) | |[1] | | | |[1] | |--------------+---------------+----------------+---------------+--------------| |endpwent |getgrnam_r |getpwnam |getutent_r |setprotoent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [2]|(GLIBC_2.2) | |[1] | | | |[1] | |--------------+---------------+----------------+---------------+--------------| |endservent |gethostbyaddr |getpwnam_r |getutxent |setpwent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[1] | | | |[1] | |--------------+---------------+----------------+---------------+--------------| |endutent |gethostbyname |getpwuid |getutxid |setservent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[3] | | | |[1] | |--------------+---------------+----------------+---------------+--------------| |endutxent |getnetbyaddr |getpwuid_r |getutxline |setutent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[1] | | | |[2] | |--------------+---------------+----------------+---------------+--------------| |getgrent |getprotobyname |getservbyname |pututxline |setutxent | |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) | |[1] | | | |[1] | +------------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [2]. Linux Standard Base [3]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) ------------------------------------------------------------------------------- Language Support ------------------------------------------------------------------------------- Interfaces for Language Support An LSB conforming implementation shall provide the architecture specific functions for Language Support specified in Table 1-24, with the full functionality as described in the referenced underlying specification. Table 1-24. libc - Language Support Function Interfaces +-----------------------------------------------------------------------------+ |__libc_start_main |_obstack_begin |_obstack_newchunk |obstack_free | | |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Large File Support ------------------------------------------------------------------------------- Interfaces for Large File Support An LSB conforming implementation shall provide the architecture specific functions for Large File Support specified in Table 1-25, with the full functionality as described in the referenced underlying specification. Table 1-25. libc - Large File Support Function Interfaces +------------------------------------------------------------------------------+ |__fxstat64 |fopen64 |ftello64 |lseek64 |readdir64 | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]| | | | |[2] | | |---------------+---------------+---------------+--------------+---------------| |__lxstat64 |freopen64 |ftruncate64 |mkstemp64 |statvfs64 | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]| | | | |[2] | | |---------------+---------------+---------------+--------------+---------------| |__xstat64 |fseeko64 |ftw64 |mmap64 |tmpfile64 | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]| | | | |[2] | | |---------------+---------------+---------------+--------------+---------------| |creat64 |fsetpos64 |getrlimit64 |nftw64 |truncate64 | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) |(GLIBC_2.2) [2]| | | | |[2] | | |---------------+---------------+---------------+--------------+---------------| |fgetpos64 |fstatvfs64 |lockf64 |open64 | | |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) [2]|(GLIBC_2.2) | | | | | |[2] | | +------------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. Large File Support ------------------------------------------------------------------------------- Standard Library ------------------------------------------------------------------------------- Interfaces for Standard Library An LSB conforming implementation shall provide the architecture specific functions for Standard Library specified in Table 1-26, with the full functionality as described in the referenced underlying specification. Table 1-26. libc - Standard Library Function Interfaces +-----------------------------------------------------------------------------+ |_Exit(GLIBC_2.2)|dirname |glob |lsearch |srand | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__assert_fail |div(GLIBC_2.2) |glob64 |makecontext |srand48 | |(GLIBC_2.2) [2] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[2] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__cxa_atexit |drand48 |globfree |malloc |srandom | |(GLIBC_2.2) [2] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__errno_location|ecvt(GLIBC_2.2) |globfree64 |memmem |strtod | |(GLIBC_2.2) [2] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2) | | | |[2] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__fpending |erand48 |grantpt |mkstemp |strtol | |(GLIBC_2.2) [2] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__getpagesize |err(GLIBC_2.2) |hcreate |mktemp |strtoul | |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__isinf |error(GLIBC_2.2)|hdestroy |mrand48 |swapcontext | |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__isinff |errx(GLIBC_2.2) |hsearch |nftw(GLIBC_2.2)|syslog | |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) |[1] |(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__isinfl |fcvt(GLIBC_2.2) |htonl |nrand48 |system | |(GLIBC_2.2) [2] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[2] | |----------------+----------------+-------------+---------------+-------------| |__isnan |fmtmsg |htons |ntohl |tdelete | |(GLIBC_2.2) [2] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__isnanf |fnmatch |imaxabs |ntohs |tfind | |(GLIBC_2.2) [2] |(GLIBC_2.2.3) |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | |[1] |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__isnanl |fpathconf |imaxdiv |openlog |tmpfile | |(GLIBC_2.2) [2] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |__sysconf |free(GLIBC_2.2) |inet_addr |perror |tmpnam | |(GLIBC_2.2) [2] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |_exit(GLIBC_2.2)|freeaddrinfo |inet_ntoa |posix_memalign |tsearch | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |_longjmp |ftrylockfile |inet_ntop |ptsname |ttyname | |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |_setjmp |ftw(GLIBC_2.2) |inet_pton |putenv |ttyname_r | |(GLIBC_2.2) [1] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |a64l(GLIBC_2.2) |funlockfile |initstate |qsort |twalk | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |abort(GLIBC_2.2)|gai_strerror |insque |rand(GLIBC_2.2)|unlockpt | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |[1] |(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |abs(GLIBC_2.2) |gcvt(GLIBC_2.2) |isatty |rand_r |unsetenv | |[1] |[1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |atof(GLIBC_2.2) |getaddrinfo |isblank |random |usleep | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |atoi(GLIBC_2.2) |getcwd |jrand48 |random_r |verrx | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2) | | | |[1] | |[2] | |----------------+----------------+-------------+---------------+-------------| |atol(GLIBC_2.2) |getdate |l64a |realloc |vfscanf | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |atoll(GLIBC_2.2)|getenv |labs |realpath |vscanf | |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.3) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |basename |getlogin |lcong48 |remque |vsscanf | |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |bsearch |getnameinfo |ldiv |seed48 |vsyslog | |(GLIBC_2.2) [1] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[2] | |----------------+----------------+-------------+---------------+-------------| |calloc |getopt |lfind |setenv |warn | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[2] | |----------------+----------------+-------------+---------------+-------------| |closelog |getopt_long |llabs |sethostid |warnx | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2) | | | |[1] | |[2] | |----------------+----------------+-------------+---------------+-------------| |confstr |getopt_long_only|lldiv |sethostname |wordexp | |(GLIBC_2.2) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) [2]|(GLIBC_2.2.2)| | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |cuserid |getsubopt |longjmp |setlogmask |wordfree | |(GLIBC_2.2) [3] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]|(GLIBC_2.2) | | | |[1] | |[1] | |----------------+----------------+-------------+---------------+-------------| |daemon |gettimeofday |lrand48 |setstate | | |(GLIBC_2.2) [2] |(GLIBC_2.2) [1] |(GLIBC_2.2) |(GLIBC_2.2) [1]| | | | |[1] | | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [2]. Linux Standard Base [3]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) An LSB conforming implementation shall provide the architecture specific data interfaces for Standard Library specified in Table 1-27, with the full functionality as described in the referenced underlying specification. Table 1-27. libc - Standard Library Data Interfaces +-----------------------------------------------------------------------------+ |__environ |_sys_errlist |getdate_err |opterr |optopt | |(GLIBC_2.2) [1]|(GLIBC_2.3) [1] |(GLIBC_2.2) [2] |(GLIBC_2.2) |(GLIBC_2.2) | | | | |[1] |[1] | |---------------+----------------+----------------+-------------+-------------| |_environ |environ |optarg |optind | | |(GLIBC_2.2) [1]|(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) | | | | | |[1] | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Data Definitions for libc This section defines global identifiers and their values that are associated with interfaces contained in libc. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. These definitions are intended to supplement those provided in the referenced underlying specifications. This specification uses ISO/IEC 9899 C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages. ------------------------------------------------------------------------------- errno.h #define EDEADLOCK EDEADLK ------------------------------------------------------------------------------- inttypes.h typedef long intmax_t; typedef unsigned long uintmax_t; typedef unsigned long uintptr_t; typedef unsigned long uint64_t; ------------------------------------------------------------------------------- limits.h #define LONG_MAX 0x7FFFFFFFFFFFFFFFL #define ULONG_MAX 0xFFFFFFFFFFFFFFFFUL #define CHAR_MAX SCHAR_MAX #define CHAR_MIN SCHAR_MIN ------------------------------------------------------------------------------- setjmp.h typedef long __jmp_buf[70] __attribute__ ((aligned (16))); ------------------------------------------------------------------------------- signal.h struct sigaction { union { sighandler_t _sa_handler; void (*_sa_sigaction) (int, siginfo_t *, void *); } __sigaction_handler; unsigned long sa_flags; sigset_t sa_mask; } ; #define MINSIGSTKSZ 131027 #define SIGSTKSZ 262144 struct ia64_fpreg { union { unsigned long bits[2]; long double __dummy; } u; } ; struct sigcontext { unsigned long sc_flags; unsigned long sc_nat; stack_t sc_stack; unsigned long sc_ip; unsigned long sc_cfm; unsigned long sc_um; unsigned long sc_ar_rsc; unsigned long sc_ar_bsp; unsigned long sc_ar_rnat; unsigned long sc_ar_ccv; unsigned long sc_ar_unat; unsigned long sc_ar_fpsr; unsigned long sc_ar_pfs; unsigned long sc_ar_lc; unsigned long sc_pr; unsigned long sc_br[8]; unsigned long sc_gr[32]; struct ia64_fpreg sc_fr[128]; unsigned long sc_rbs_base; unsigned long sc_loadrs; unsigned long sc_ar25; unsigned long sc_ar26; unsigned long sc_rsvd[12]; unsigned long sc_mask; } ; ------------------------------------------------------------------------------- stddef.h typedef long ptrdiff_t; typedef unsigned long size_t; ------------------------------------------------------------------------------- sys/ioctl.h #define FIONREAD 0x541B #define TIOCNOTTY 0x5422 ------------------------------------------------------------------------------- sys/ipc.h struct ipc_perm { key_t __key; uid_t uid; gid_t gid; uid_t cuid; uid_t cgid; mode_t mode; unsigned short __seq; unsigned short __pad1; unsigned long __unused1; unsigned long __unused2; } ; ------------------------------------------------------------------------------- sys/mman.h #define MCL_CURRENT 1 #define MCL_FUTURE 2 ------------------------------------------------------------------------------- sys/msg.h struct msqid_ds { struct ipc_perm msg_perm; time_t msg_stime; time_t msg_rtime; time_t msg_ctime; unsigned long __msg_cbytes; unsigned long msg_qnum; unsigned long msg_qbytes; pid_t msg_lspid; pid_t msg_lrpid; unsigned long __unused1; unsigned long __unused2; } ; ------------------------------------------------------------------------------- sys/sem.h struct semid_ds { struct ipc_perm sem_perm; time_t sem_otime; time_t sem_ctime; unsigned long sem_nsems; unsigned long __unused1; unsigned long __unused2; } ; ------------------------------------------------------------------------------- sys/shm.h #define SHMLBA (1024*1024) struct shmid_ds { struct ipc_perm shm_perm; size_t shm_segsz; time_t shm_atime; time_t shm_dtime; time_t shm_ctime; pid_t shm_cpid; pid_t shm_lpid; unsigned long shm_nattch; unsigned long __unused1; unsigned long __unused2; } ; ------------------------------------------------------------------------------- sys/socket.h typedef uint64_t __ss_aligntype; ------------------------------------------------------------------------------- sys/stat.h #define _STAT_VER 1 struct stat { dev_t st_dev; ino_t st_ino; nlink_t st_nlink; mode_t st_mode; uid_t st_uid; gid_t st_gid; unsigned int pad0; dev_t st_rdev; off_t st_size; struct timespec st_atim; struct timespec st_mtim; struct timespec st_ctim; blksize_t st_blksize; blkcnt_t st_blocks; unsigned long __unused[3]; } ; struct stat64 { dev_t st_dev; ino64_t st_ino; nlink_t st_nlink; mode_t st_mode; uid_t st_uid; gid_t st_gid; unsigned int pad0; dev_t st_rdev; off_t st_size; struct timespec st_atim; struct timespec st_mtim; struct timespec st_ctim; blksize_t st_blksize; blkcnt64_t st_blocks; unsigned long __unused[3]; } ; ------------------------------------------------------------------------------- sys/statvfs.h struct statvfs { unsigned long f_bsize; unsigned long f_frsize; fsblkcnt64_t f_blocks; fsblkcnt64_t f_bfree; fsblkcnt64_t f_bavail; fsfilcnt64_t f_files; fsfilcnt64_t f_ffree; fsfilcnt64_t f_favail; unsigned long f_fsid; unsigned long f_flag; unsigned long f_namemax; unsigned int __f_spare[6]; } ; struct statvfs64 { unsigned long f_bsize; unsigned long f_frsize; fsblkcnt64_t f_blocks; fsblkcnt64_t f_bfree; fsblkcnt64_t f_bavail; fsfilcnt64_t f_files; fsfilcnt64_t f_ffree; fsfilcnt64_t f_favail; unsigned long f_fsid; unsigned long f_flag; unsigned long f_namemax; unsigned int __f_spare[6]; } ; ------------------------------------------------------------------------------- sys/types.h typedef long int64_t; typedef int64_t ssize_t; ------------------------------------------------------------------------------- termios.h #define OLCUC 0000002 #define ONLCR 0000004 #define XCASE 0000004 #define NLDLY 0000400 #define CR1 0001000 #define IUCLC 0001000 #define CR2 0002000 #define CR3 0003000 #define CRDLY 0003000 #define TAB1 0004000 #define TAB2 0010000 #define TAB3 0014000 #define TABDLY 0014000 #define BS1 0020000 #define BSDLY 0020000 #define VT1 0040000 #define VTDLY 0040000 #define FF1 0100000 #define FFDLY 0100000 #define VSUSP 10 #define VEOL 11 #define VREPRINT 12 #define VDISCARD 13 #define VWERASE 14 #define VEOL2 16 #define VMIN 6 #define VSWTC 7 #define VSTART 8 #define VSTOP 9 #define IXON 0002000 #define IXOFF 0010000 #define CS6 0000020 #define CS7 0000040 #define CS8 0000060 #define CSIZE 0000060 #define CSTOPB 0000100 #define CREAD 0000200 #define PARENB 0000400 #define PARODD 0001000 #define HUPCL 0002000 #define CLOCAL 0004000 #define VTIME 5 #define ISIG 0000001 #define ICANON 0000002 #define ECHOE 0000020 #define ECHOK 0000040 #define ECHONL 0000100 #define NOFLSH 0000200 #define TOSTOP 0000400 #define ECHOCTL 0001000 #define ECHOPRT 0002000 #define ECHOKE 0004000 #define FLUSHO 0010000 #define PENDIN 0040000 #define IEXTEN 0100000 ------------------------------------------------------------------------------- ucontext.h #define _SC_GR0_OFFSET (((char *) & ((struct sigcontext *) 0)->sc_gr[0]) - (char *) 0) typedef struct sigcontext mcontext_t; typedef struct ucontext { union { mcontext_t _mc; struct { unsigned long _pad[_SC_GR0_OFFSET / 8]; struct ucontext *_link; } _uc; } _u; } ucontext_t; ------------------------------------------------------------------------------- unistd.h typedef long intptr_t; ------------------------------------------------------------------------------- utmp.h struct lastlog { int32_t ll_time; char ll_line[UT_LINESIZE]; char ll_host[UT_HOSTSIZE]; } ; struct utmp { short ut_type; pid_t ut_pid; char ut_line[UT_LINESIZE]; char ut_id[4]; char ut_user[UT_NAMESIZE]; char ut_host[UT_HOSTSIZE]; struct exit_status ut_exit; long ut_session; struct timeval ut_tv; int32_t ut_addr_v6[4]; char __unused[20]; } ; ------------------------------------------------------------------------------- utmpx.h struct utmpx { short ut_type; pid_t ut_pid; char ut_line[UT_LINESIZE]; char ut_id[4]; char ut_user[UT_NAMESIZE]; char ut_host[UT_HOSTSIZE]; struct exit_status ut_exit; long ut_session; struct timeval ut_tv; int32_t ut_addr_v6[4]; char __unused[20]; } ; ------------------------------------------------------------------------------- Interfaces for libm Table 1-28 defines the library name and shared object name for the libm library Table 1-28. libm Definition +---------------------+ |Library:|libm | |--------+------------| |SONAME: |libm.so.6.1 | +---------------------+ The behavior of the interfaces in this library is specified by the following specifications: ISO/IEC 9899: 1999, Programming Languages --C CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Math ------------------------------------------------------------------------------- Interfaces for Math An LSB conforming implementation shall provide the architecture specific functions for Math specified in Table 1-29, with the full functionality as described in the referenced underlying specification. Table 1-29. libm - Math Function Interfaces +-----------------------------------------------------------------------------+ |acos |cexp |expf(GLIBC_2.2) |jnf(GLIBC_2.2) |remquof | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[2] |(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |acosf |cexpf |expl(GLIBC_2.2) |jnl(GLIBC_2.2) |remquol | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[2] |(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |acosh |cexpl |expm1(GLIBC_2.2) |ldexp |rint(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |acoshf |cimag |fabs(GLIBC_2.2) |ldexpf |rintf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |acoshl |cimagf |fabsf(GLIBC_2.2) |ldexpl |rintl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |acosl |cimagl |fabsl(GLIBC_2.2) |lgamma |round | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |asin |clog |fdim(GLIBC_2.2) |lgamma_r |roundf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [2]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |asinf |clog10 |fdimf(GLIBC_2.2) |lgammaf |roundl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[2] | | | | |------------+--------------+-----------------+---------------+---------------| |asinh |clog10f |fdiml(GLIBC_2.2) |lgammaf_r |scalb | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [2]|(GLIBC_2.2) [1]| |[1] |[2] | | | | |------------+--------------+-----------------+---------------+---------------| |asinhf |clog10l |feclearexcept |lgammal |scalbf | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]| |[1] |[2] | | | | |------------+--------------+-----------------+---------------+---------------| |asinhl |clogf |fegetenv |lgammal_r |scalbl | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [2]|(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |asinl |clogl |fegetexceptflag |llrint |scalbln | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atan |conj |fegetround |llrintf |scalblnf | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atan2 |conjf |feholdexcept |llrintl |scalblnl | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atan2f |conjl |feraiseexcept |llround |scalbn | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atan2l |copysign |fesetenv |llroundf |scalbnf | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atanf |copysignf |fesetexceptflag |llroundl |scalbnl | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atanh |copysignl |fesetround |log(GLIBC_2.2) |significand | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |[1] |(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atanhf |cos(GLIBC_2.2)|fetestexcept |log10 |significandf | |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]| |[1] | | | | | |------------+--------------+-----------------+---------------+---------------| |atanhl |cosf |feupdateenv |log10f |significandl | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |atanl |cosh |finite(GLIBC_2.2)|log10l |sin(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[3] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cabs |coshf |finitef |log1p |sincos | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |(GLIBC_2.2) [1]|(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cabsf |coshl |finitel |logb(GLIBC_2.2)|sincosf | |(GLIBC_2.2) |(GLIBC_2.2) |(GLIBC_2.2) [2] |[1] |(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cabsl |cosl |floor(GLIBC_2.2) |logf(GLIBC_2.2)|sincosl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |(GLIBC_2.2) [2]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacos |cpow |floorf(GLIBC_2.2)|logl(GLIBC_2.2)|sinf(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacosf |cpowf |floorl(GLIBC_2.2)|lrint |sinh(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacosh |cpowl |fma(GLIBC_2.2) |lrintf |sinhf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacoshf |cproj |fmaf(GLIBC_2.2) |lrintl |sinhl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacoshl |cprojf |fmal(GLIBC_2.2) |lround |sinl(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cacosl |cprojl |fmax(GLIBC_2.2) |lroundf |sqrt(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |carg |creal |fmaxf(GLIBC_2.2) |lroundl |sqrtf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cargf |crealf |fmaxl(GLIBC_2.2) |matherr |sqrtl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [2]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cargl |creall |fmin(GLIBC_2.2) |modf(GLIBC_2.2)|tan(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casin |csin |fminf(GLIBC_2.2) |modff |tanf(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casinf |csinf |fminl(GLIBC_2.2) |modfl |tanh(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casinh |csinh |fmod(GLIBC_2.2) |nan(GLIBC_2.2) |tanhf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casinhf |csinhf |fmodf(GLIBC_2.2) |nanf(GLIBC_2.2)|tanhl | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casinhl |csinhl |fmodl(GLIBC_2.2) |nanl(GLIBC_2.2)|tanl(GLIBC_2.2)| |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |casinl |csinl |frexp(GLIBC_2.2) |nearbyint |tgamma | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catan |csqrt |frexpf(GLIBC_2.2)|nearbyintf |tgammaf | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catanf |csqrtf |frexpl(GLIBC_2.2)|nearbyintl |tgammal | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catanh |csqrtl |gamma(GLIBC_2.2) |nextafter |trunc | |(GLIBC_2.2) |(GLIBC_2.2) |[3] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catanhf |ctan |gammaf(GLIBC_2.2)|nextafterf |truncf | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catanhl |ctanf |gammal(GLIBC_2.2)|nextafterl |truncl | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |catanl |ctanh |hypot(GLIBC_2.2) |nexttoward |y0(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cbrt |ctanhf |hypotf(GLIBC_2.2)|nexttowardf |y0f(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[2] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cbrtf |ctanhl |hypotl(GLIBC_2.2)|nexttowardl |y0l(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [1]|[2] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |cbrtl |ctanl |ilogb(GLIBC_2.2) |pow(GLIBC_2.2) |y1(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |[1] |[1] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ccos |dremf |ilogbf(GLIBC_2.2)|pow10 |y1f(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [2]|[2] | |[1] |[2] | | | | |------------+--------------+-----------------+---------------+---------------| |ccosf |dreml |ilogbl(GLIBC_2.2)|pow10f |y1l(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[1] |(GLIBC_2.2) [2]|[2] | |[1] |[2] | | | | |------------+--------------+-----------------+---------------+---------------| |ccosh |erf(GLIBC_2.2)| |pow10l |yn(GLIBC_2.2) | |(GLIBC_2.2) |[1] |j0(GLIBC_2.2) [1]|(GLIBC_2.2) [2]|[1] | |[1] | | | | | |------------+--------------+-----------------+---------------+---------------| |ccoshf |erfc |j0f(GLIBC_2.2) |powf(GLIBC_2.2)|ynf(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |[1] |[2] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ccoshl |erfcf |j0l(GLIBC_2.2) |powl(GLIBC_2.2)|ynl(GLIBC_2.2) | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |[1] |[2] | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ccosl |erfcl | |remainder | | |(GLIBC_2.2) |(GLIBC_2.2) |j1(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ceil |erff |j1f(GLIBC_2.2) |remainderf | | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) [1]| | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ceilf |erfl |j1l(GLIBC_2.2) |remainderl | | |(GLIBC_2.2) |(GLIBC_2.2) |[2] |(GLIBC_2.2) [1]| | |[1] |[1] | | | | |------------+--------------+-----------------+---------------+---------------| |ceill |exp(GLIBC_2.2)| |remquo | | |(GLIBC_2.2) |[1] |jn(GLIBC_2.2) [1]|(GLIBC_2.2) [1]| | |[1] | | | | | +-----------------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [2]. ISO/IEC 9899: 1999, Programming Languages --C [3]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) An LSB conforming implementation shall provide the architecture specific data interfaces for Math specified in Table 1-30, with the full functionality as described in the referenced underlying specification. Table 1-30. libm - Math Data Interfaces +-------------------------------+ |signgam(GLIBC_2.2) [1] | | | | | +-------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Interfaces for libpthread Table 1-31 defines the library name and shared object name for the libpthread library Table 1-31. libpthread Definition +-------------------------+ |Library:|libpthread | |--------+----------------| |SONAME: |libpthread.so.0 | +-------------------------+ The behavior of the interfaces in this library is specified by the following specifications: Large File Support Linux Standard Base ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Realtime Threads ------------------------------------------------------------------------------- Interfaces for Realtime Threads No external functions are defined for libpthread - Realtime Threads ------------------------------------------------------------------------------- Advanced Realtime Threads ------------------------------------------------------------------------------- Interfaces for Advanced Realtime Threads No external functions are defined for libpthread - Advanced Realtime Threads ------------------------------------------------------------------------------- Posix Threads ------------------------------------------------------------------------------- Interfaces for Posix Threads An LSB conforming implementation shall provide the architecture specific functions for Posix Threads specified in Table 1-32, with the full functionality as described in the referenced underlying specification. Table 1-32. libpthread - Posix Threads Function Interfaces +-----------------------------------------------------------------------------------------------------------------------------------------+ |_pthread_cleanup_pop |pthread_cancel(GLIBC_2.2) |pthread_join(GLIBC_2.2) [2] |pthread_rwlock_destroy |pthread_setconcurrency| |(GLIBC_2.2) [1] |[2] | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |_pthread_cleanup_push |pthread_cond_broadcast |pthread_key_create |pthread_rwlock_init |pthread_setspecific | |(GLIBC_2.2) [1] |(GLIBC_2.3.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pread(GLIBC_2.2) [2] |pthread_cond_destroy |pthread_key_delete |pthread_rwlock_rdlock |pthread_sigmask | | |(GLIBC_2.3.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pread64(GLIBC_2.2) [3] |pthread_cond_init |pthread_kill(GLIBC_2.2) [2] |pthread_rwlock_timedrdlock |pthread_testcancel | | |(GLIBC_2.3.2) [2] | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_destroy |pthread_cond_signal |pthread_mutex_destroy |pthread_rwlock_timedwrlock |pwrite(GLIBC_2.2) [2] | |(GLIBC_2.2) [2] |(GLIBC_2.3.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_getdetachstate|pthread_cond_timedwait |pthread_mutex_init |pthread_rwlock_tryrdlock |pwrite64(GLIBC_2.2) | |(GLIBC_2.2) [2] |(GLIBC_2.3.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[3] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_getguardsize |pthread_cond_wait |pthread_mutex_lock |pthread_rwlock_trywrlock |sem_close(GLIBC_2.2) | |(GLIBC_2.2) [2] |(GLIBC_2.3.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_getschedparam |pthread_condattr_destroy |pthread_mutex_trylock |pthread_rwlock_unlock |sem_destroy(GLIBC_2.2)| |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_getstackaddr |pthread_condattr_getpshared|pthread_mutex_unlock |pthread_rwlock_wrlock |sem_getvalue | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_getstacksize |pthread_condattr_init |pthread_mutexattr_destroy |pthread_rwlockattr_destroy |sem_init(GLIBC_2.2) | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_init |pthread_condattr_setpshared|pthread_mutexattr_getpshared|pthread_rwlockattr_getpshared|sem_open(GLIBC_2.2) | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_setdetachstate|pthread_create(GLIBC_2.2) |pthread_mutexattr_gettype |pthread_rwlockattr_init |sem_post(GLIBC_2.2) | |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_setguardsize |pthread_detach(GLIBC_2.2) |pthread_mutexattr_init |pthread_rwlockattr_setpshared|sem_timedwait | |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_setschedparam |pthread_equal(GLIBC_2.2) |pthread_mutexattr_setpshared|pthread_self(GLIBC_2.2) [2] |sem_trywait(GLIBC_2.2)| |(GLIBC_2.2) [2] |[2] |(GLIBC_2.2) [2] | |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_setstackaddr |pthread_exit(GLIBC_2.2) [2]|pthread_mutexattr_settype |pthread_setcancelstate |sem_unlink(GLIBC_2.2) | |(GLIBC_2.2) [2] | |(GLIBC_2.2) [2] |(GLIBC_2.2) [2] |[2] | |---------------------------+---------------------------+----------------------------+-----------------------------+----------------------| |pthread_attr_setstacksize |pthread_getspecific |pthread_once(GLIBC_2.2) [2] |pthread_setcanceltype |sem_wait(GLIBC_2.2) | |(GLIBC_2.3.3) [2] |(GLIBC_2.2) [2] | |(GLIBC_2.2) [2] |[2] | +-----------------------------------------------------------------------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 [3]. Large File Support ------------------------------------------------------------------------------- Interfaces for libgcc_s Table 1-33 defines the library name and shared object name for the libgcc_s library Table 1-33. libgcc_s Definition +-----------------------+ |Library:|libgcc_s | |--------+--------------| |SONAME: |libgcc_s.so.1 | +-----------------------+ The behavior of the interfaces in this library is specified by the following specifications: Linux Standard Base ------------------------------------------------------------------------------- Unwind Library ------------------------------------------------------------------------------- Interfaces for Unwind Library An LSB conforming implementation shall provide the architecture specific functions for Unwind Library specified in Table 1-34, with the full functionality as described in the referenced underlying specification. Table 1-34. libgcc_s - Unwind Library Function Interfaces +----------------------------------------------------------------------------------------------------------+ |_Unwind_DeleteException|_Unwind_GetGR|_Unwind_GetLanguageSpecificData|_Unwind_RaiseException|_Unwind_SetGR| |(GCC_3.0) [1] |(GCC_3.0) [1]|(GCC_3.0) [1] |(GCC_3.0) [1] |(GCC_3.0) [1]| |-----------------------+-------------+-------------------------------+----------------------+-------------| |_Unwind_ForcedUnwind |_Unwind_GetIP|_Unwind_GetRegionStart(GCC_3.0)|_Unwind_Resume |_Unwind_SetIP| |(GCC_3.0) [1] |(GCC_3.0) [1]|[1] |(GCC_3.0) [1] |(GCC_3.0) [1]| +----------------------------------------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Interface Definitions for libgcc_s Table of Contents _Unwind_DeleteException -- private C++ error handling method _Unwind_ForcedUnwind -- private 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_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 The following interfaces are included in libgcc_s and are defined by this specification. Unless otherwise noted, these interfaces shall be included in the source standard. Other interfaces listed above for libgcc_s shall behave as described in the referenced base document. _Unwind_DeleteException Name _Unwind_DeleteException -- private C++ error handling method Synopsis void _Unwind_DeleteException((struct _Unwind_Exception *object)); Description _Unwind_DeleteException deletes the given exception object. If a given runtime resumes normal execution after catching a foreign exception, it will not know how to delete that exception. Such an exception shall be deleted by calling _Unwind_DeleteException. This is a convenience function that calls the function pointed to by the exception_cleanup field of the exception header. _Unwind_ForcedUnwind Name _Unwind_ForcedUnwind -- private C++ error handling method Synopsis _Unwind_Reason_Code _Unwind_ForcedUnwind((struct _Unwind_Exception *object), _Unwind_Stop_Fn stop, void *stop_parameter); Description _Unwind_ForcedUnwind raises an exception for forced unwinding, passing along the given exception object, which should have its exception_class and exception_cleanup fields set. The exception object has been allocated by the language-specific runtime, and has a language-specific format, except that it shall contain an _Unwind_Exception struct. Forced unwinding is a single-phase process. stop and stop_parameter control the termination of the unwind process instead of the usual personality routine query. stop is called for each unwind frame, with the parameteres described for the usual personality routine below, plus an additional stop_parameter. Return Value When stop identifies the destination frame, it transfers control to the user code as appropriate without returning, normally after calling _Unwind_DeleteException. If not, then it should return an _Unwind_Reason_Code value. If stop returns any reason code other than _URC_NO_REASON, then the stack state is indeterminate from the point of view of the caller of _Unwind_ForcedUnwind. Rather than attempt to return, therefore, the unwind library should use the exception_cleanup entry in the exception, and then call abort. _URC_NO_REASON This is not the destination from. The unwind runtime will call frame's personality routine with the _UA_FORCE_UNWIND and _UA_CLEANUP_PHASE flag set in actions, and then unwind to the next frame and call the stop function again. _URC_END_OF_STACK In order to allow _Unwind_ForcedUnwind to perform special processing when it reaches the end of the stack, the unwind runtime will call it after the last frame is rejected, with a NULL stack pointer in the context, and the stop function shall catch this condition. It may return this code if it cannot handle end-of-stack. _URC_FATAL_PHASE2_ERROR The stop function may return this code for other fatal conditions like stack corruption. _Unwind_GetGR Name _Unwind_GetGR -- private C++ error handling method Synopsis _Unwind_Word _Unwind_GetGR((struct _Unwind_Context *context), int index); Description _Unwind_GetGR returns data at index found in context. The register is identified by its index: 0 to 31 are for the fixed registers, and 32 to 127 are for the stacked registers. During the two phases of unwinding, only GR1 has a guaranteed value, which is the global pointer of the frame referenced by the unwind context. If the register has its NAT bit set, the behavior is unspecified. _Unwind_GetIP Name _Unwind_GetIP -- private C++ error handling method Synopsis _Unwind_Ptr _Unwind_GetIP((struct _Unwind_Context *context)); Description _Unwind_GetIP returns the instruction pointer value for the routine identified by the unwind context. _Unwind_GetLanguageSpecificData Name _Unwind_GetLanguageSpecificData -- private C++ error handling method Synopsis _Unwind_Ptr _Unwind_GetLanguageSpecificData((struct _Unwind_Context *context), uint value); Description _Unwind_GetLanguageSpecificData returns the address of the language specific data area for the current stack frame. _Unwind_GetRegionStart Name _Unwind_GetRegionStart -- private C++ error handling method Synopsis _Unwind_Ptr _Unwind_GetRegionStart((struct _Unwind_Context *context)); Description _Unwind_GetRegionStart routine returns the address (i.e., 0) of the beginning of the procedure or code fragment described by the current unwind descriptor block. _Unwind_RaiseException Name _Unwind_RaiseException -- private C++ error handling method Synopsis _Unwind_Reason_Code _Unwind_RaiseException((struct _Unwind_Exception *object)); Description _Unwind_RaiseException raises an exception, passing along the given exception object, which should have its exception_class and exception_cleanup fields set. The exception object has been allocated by the language-specific runtime, and has a language-specific format, exception that it shall contain an _Unwind_Exception. Return Value _Unwind_RaiseException does not return unless an error condition is found. If an error condition occurs, an _Unwind_Reason_Code is returnd: _URC_END_OF_STACK The unwinder encountered the end of the stack during phase one without finding a handler. The unwind runtime will not have modified the stack. The C++ runtime will normally call uncaught_exception in this case. _URC_FATAL_PHASE1_ERROR The unwinder encountered an unexpected error during phase one, because of something like stack corruption. The unwind runtime will not have modified the stack. The C++ runtime will normally call terminate in this case. _URC_FATAL_PHASE2_ERROR The unwinder encountered an unexpected error during phase two. This is usually a throw, which will call terminate. _Unwind_Resume Name _Unwind_Resume -- private C++ error handling method Synopsis void _Unwind_Resume((struct _Unwind_Exception *object)); Description _Unwind_Resume resumes propagation of an existing exception object. A call to this routine is inserted as the end of a landing pad that performs cleanup, but does not resume normal execution. It causes unwinding to proceed further. _Unwind_SetGR Name _Unwind_SetGR -- private C++ error handling method Synopsis void _Unwind_SetGR((struct _Unwind_Context *context), int index, uint value); Description _Unwind_SetGR sets the value of the register indexed for the routine identified by the unwind context. _Unwind_SetIP Name _Unwind_SetIP -- private C++ error handling method Synopsis void _Unwind_SetIP((struct _Unwind_Context *context), uint value); Description _Unwind_SetIP sets the value of the instruction pointer for the routine identified by the unwind context ------------------------------------------------------------------------------- Interfaces for libdl Table 1-35 defines the library name and shared object name for the libdl library Table 1-35. libdl Definition +--------------------+ |Library:|libdl | |--------+-----------| |SONAME: |libdl.so.2 | +--------------------+ The behavior of the interfaces in this library is specified by the following specifications: Linux Standard Base ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Dynamic Loader ------------------------------------------------------------------------------- Interfaces for Dynamic Loader An LSB conforming implementation shall provide the architecture specific functions for Dynamic Loader specified in Table 1-36, with the full functionality as described in the referenced underlying specification. Table 1-36. libdl - Dynamic Loader Function Interfaces +------------------------------------------------------------------------------+ |dladdr |dlclose |dlerror |dlopen |dlsym | |(GLIBC_2.0) [1]|(GLIBC_2.0) [2]|(GLIBC_2.0) [2]|(GLIBC_2.1) [1]|(GLIBC_2.0) | | | | | |[1] | +------------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base [2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Interfaces for libcrypt Table 1-37 defines the library name and shared object name for the libcrypt library Table 1-37. libcrypt Definition +-----------------------+ |Library:|libcrypt | |--------+--------------| |SONAME: |libcrypt.so.1 | +-----------------------+ The behavior of the interfaces in this library is specified by the following specifications: ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 ------------------------------------------------------------------------------- Encryption ------------------------------------------------------------------------------- Interfaces for Encryption An LSB conforming implementation shall provide the architecture specific functions for Encryption specified in Table 1-38, with the full functionality as described in the referenced underlying specification. Table 1-38. libcrypt - Encryption Function Interfaces +---------------------------------------------------------------------+ |crypt(GLIBC_2.0) [1]|encrypt(GLIBC_2.0) [1]|setkey(GLIBC_2.0) [1]| | | +---------------------------------------------------------------------+ Referenced Specification(s) [1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX Specification(SUS) V3 II. Utility Libraries Table of Contents 2. Libraries ------------------------------------------------------------------------------- Chapter 2. Libraries The Utility libraries are those that are commonly used, but not part of the Single Unix Specification. ------------------------------------------------------------------------------- Interfaces for libz Table 2-1 defines the library name and shared object name for the libz library Table 2-1. libz Definition +-------------------+ |Library:|libz | |--------+----------| |SONAME: |libz.so.1 | +-------------------+ ------------------------------------------------------------------------------- Compression Library ------------------------------------------------------------------------------- Interfaces for Compression Library No external functions are defined for libz - Compression Library ------------------------------------------------------------------------------- Interfaces for libncurses Table 2-2 defines the library name and shared object name for the libncurses library Table 2-2. libncurses Definition +-------------------------+ |Library:|libncurses | |--------+----------------| |SONAME: |libncurses.so.5 | +-------------------------+ ------------------------------------------------------------------------------- Curses ------------------------------------------------------------------------------- Interfaces for Curses No external functions are defined for libncurses - Curses ------------------------------------------------------------------------------- Interfaces for libutil Table 2-3 defines the library name and shared object name for the libutil library Table 2-3. libutil Definition +----------------------+ |Library:|libutil | |--------+-------------| |SONAME: |libutil.so.1 | +----------------------+ The behavior of the interfaces in this library is specified by the following specifications: Linux Standard Base ------------------------------------------------------------------------------- Utility Functions ------------------------------------------------------------------------------- Interfaces for Utility Functions An LSB conforming implementation shall provide the architecture specific functions for Utility Functions specified in Table 2-4, with the full functionality as described in the referenced underlying specification. Table 2-4. libutil - Utility Functions Function Interfaces +--------------------------------------------------------------------------+ |forkpty(GLIBC_2.0) [1]|login_tty(GLIBC_2.0) [1]|logwtmp(GLIBC_2.0) [1]| | | |----------------------+------------------------+----------------------+-+-| |login(GLIBC_2.0) [1] |logout(GLIBC_2.0) [1] |openpty(GLIBC_2.0) [1]| | | +--------------------------------------------------------------------------+ Referenced Specification(s) [1]. Linux Standard Base ------------------------------------------------------------------------------- Appendix A. Alphabetical Listing of Interfaces ------------------------------------------------------------------------------- libgcc_s The behaviour of the interfaces in this library is specified by the following Standards. Linux Standard Base Table A-1. libgcc_s Function Interfaces +-----------------------------------------------------------------------------+ |_Unwind_DeleteException[1]|_Unwind_GetLanguageSpecificData |_Unwind_SetGR[1]| | |[1] | | |--------------------------+---------------------------------+----------------| |_Unwind_ForcedUnwind[1] |_Unwind_GetRegionStart[1] |_Unwind_SetIP[1]| |--------------------------+---------------------------------+----------------| |_Unwind_GetGR[1] |_Unwind_RaiseException[1] | | |--------------------------+---------------------------------+----------------| |_Unwind_GetIP[1] |_Unwind_Resume[1] | | +-----------------------------------------------------------------------------+ Linux Packaging Specification ------------------------------------------------------------------------------- Table of Contents I. Package Format and Installation 1. Software Installation Package Dependencies Package Architecture Considerations I. Package Format and Installation Table of Contents 1. Software Installation ------------------------------------------------------------------------------- Chapter 1. Software Installation ------------------------------------------------------------------------------- Package Dependencies The LSB runtime environment shall provde the following dependencies. lsb-core-ia64 This dependency is used to indicate that the application is dependent on features contained in the LSB-Core specification. Other LSB modules may add additional dependencies; such dependencies shall have the format lsb-module-ia64. ------------------------------------------------------------------------------- Package Architecture Considerations All packages must specify an architecture of IA64. A LSB runtime environment must accept an architecture of IA64 even if the native architecture is different. The archnum value in the Lead Section shall be 0x0009.