Linux Standard Base Core Specification for IA64 3.1 Copyright © 2004, 2005 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. PowerPC and PowerPC Architecture are trademarks of the IBM Corporation. OpenGL is a registered trademark of Silicon Graphics, Inc. _________________________________________________________ Table of Contents Foreword Introduction I. Introductory Elements 1. Scope 1.1. General 1.2. Module Specific Scope 2. References 2.1. Normative References 2.2. Informative References/Bibliography 3. Requirements 3.1. Relevant Libraries 3.2. LSB Implementation Conformance 3.3. LSB Application Conformance 4. Definitions 5. Terminology 6. Documentation Conventions II. Executable and Linking Format (ELF) 7. Introduction 8. Low Level System Information 8.1. Machine Interface 8.2. Function Calling Sequence 8.3. Operating System Interface 8.4. Process Initialization 8.5. Coding Examples 8.6. C Stack Frame 8.7. Debug Information 9. Object Format 9.1. Introduction 9.2. ELF Header 9.3. Sections 9.4. Symbol Table 9.5. Relocation 10. Program Loading and Dynamic Linking 10.1. Introduction 10.2. Program Header 10.3. Program Loading 10.4. Dynamic Linking III. Base Libraries 11. Libraries 11.1. Program Interpreter/Dynamic Linker 11.2. Interfaces for libc 11.3. Data Definitions for libc 11.4. Interfaces for libm 11.5. Data Definitions for libm 11.6. Interfaces for libpthread 11.7. Data Definitions for libpthread 11.8. Interfaces for libgcc_s 11.9. Data Definitions for libgcc_s 11.10. Interface Definitions for libgcc_s 11.11. Interfaces for libdl 11.12. Data Definitions for libdl 11.13. Interfaces for libcrypt IV. Utility Libraries 12. Libraries 12.1. Interfaces for libz 12.2. Data Definitions for libz 12.3. Interfaces for libncurses 12.4. Data Definitions for libncurses 12.5. Interfaces for libutil V. Package Format and Installation 13. Software Installation 13.1. Package Dependencies 13.2. Package Architecture Considerations A. Alphabetical Listing of Interfaces A.1. libgcc_s A.2. libm B. GNU Free Documentation License (Informative) B.1. PREAMBLE B.2. APPLICABILITY AND DEFINITIONS B.3. VERBATIM COPYING B.4. COPYING IN QUANTITY B.5. MODIFICATIONS B.6. COMBINING DOCUMENTS B.7. COLLECTIONS OF DOCUMENTS B.8. AGGREGATION WITH INDEPENDENT WORKS B.9. TRANSLATION B.10. TERMINATION B.11. FUTURE REVISIONS OF THIS LICENSE B.12. How to use this License for your documents List of Figures 8-1. Structure Smaller Than A Word 8-2. No Padding 8-3. Internal and Tail Padding 8-4. Bit-Field Ranges List of Tables 2-1. Normative References 2-2. Other References 3-1. Standard Library Names 8-1. Scalar Types 9-1. Additional Processor-Specific Flags 9-2. ELF Special Sections 9-3. Additional Special Sections 11-1. libc Definition 11-2. libc - RPC Function Interfaces 11-3. libc - System Calls Function Interfaces 11-4. libc - Standard I/O Function Interfaces 11-5. libc - Standard I/O Data Interfaces 11-6. libc - Signal Handling Function Interfaces 11-7. libc - Signal Handling Data Interfaces 11-8. libc - Localization Functions Function Interfaces 11-9. libc - Localization Functions Data Interfaces 11-10. libc - Socket Interface Function Interfaces 11-11. libc - Wide Characters Function Interfaces 11-12. libc - String Functions Function Interfaces 11-13. libc - IPC Functions Function Interfaces 11-14. libc - Regular Expressions Function Interfaces 11-15. libc - Character Type Functions Function Interfaces 11-16. libc - Time Manipulation Function Interfaces 11-17. libc - Time Manipulation Data Interfaces 11-18. libc - Terminal Interface Functions Function Interfaces 11-19. libc - System Database Interface Function Interfaces 11-20. libc - Language Support Function Interfaces 11-21. libc - Large File Support Function Interfaces 11-22. libc - Standard Library Function Interfaces 11-23. libc - Standard Library Data Interfaces 11-24. libm Definition 11-25. libm - Math Function Interfaces 11-26. libm - Math Data Interfaces 11-27. libpthread Definition 11-28. libpthread - Realtime Threads Function Interfaces 11-29. libpthread - Posix Threads Function Interfaces 11-30. libpthread - Thread aware versions of libc interfaces Function Interfaces 11-31. libgcc_s Definition 11-32. libgcc_s - Unwind Library Function Interfaces 11-33. libdl Definition 11-34. libdl - Dynamic Loader Function Interfaces 11-35. libcrypt Definition 11-36. libcrypt - Encryption Function Interfaces 12-1. libz Definition 12-2. libncurses Definition 12-3. libutil Definition 12-4. libutil - Utility Functions Function Interfaces A-1. libgcc_s Function Interfaces A-2. libm Function Interfaces _________________________________________________________ Foreword This is version 3.1 of the Linux Standard Base Core Specification for IA64. This specification is part of a family of specifications under the general title "Linux Standard Base". Developers of applications or implementations interested in using the LSB trademark should see the Free Standards Group Certification Policy for details. _________________________________________________________ Introduction The LSB defines a binary interface for application programs that are compiled and packaged for LSB-conforming implementations on many different hardware architectures. Since a binary specification shall include information specific to the computer processor architecture for which it is intended, it is not possible for a single document to specify the interface for all possible LSB-conforming implementations. Therefore, the LSB is a family of specifications, rather than a single one. This document should be used in conjunction with the documents it references. This document enumerates the system components it includes, but descriptions of those components may be included entirely or partly in this document, partly in other documents, or entirely in other reference documents. For example, the section that describes system service routines includes a list of the system routines supported in this interface, formal declarations of the data structures they use that are visible to applications, and a pointer to the underlying referenced specification for information about the syntax and semantics of each call. Only those routines not described in standards referenced by this document, or extensions to those standards, are described in the detail. Information referenced in this way is as much a part of this document as is the information explicitly included here. The specification carries a version number of either the form x.y or x.y.z. This version number carries the following meaning: * The first number (x) is the major version number. All versions with the same major version number should share binary compatibility. Any addition or deletion of a new library results in a new version number. Interfaces marked as deprecated may be removed from the specification at a major version change. * The second number (y) is the minor version number. Individual interfaces may be added if all certified implementations already had that (previously undocumented) interface. Interfaces may be marked as deprecated at a minor version change. Other minor changes may be permitted at the discretion of the LSB workgroup. * The third number (z), if present, is the editorial level. Only editorial changes should be included in such versions. Since this specification is a descriptive Application Binary Interface, and not a source level API specification, it is not possible to make a guarantee of 100% backward compatibility between major releases. However, it is the intent that those parts of the binary interface that are visible in the source level API will remain backward compatible from version to version, except where a feature marked as "Deprecated" in one release may be removed from a future release. Implementors are strongly encouraged to make use of symbol versioning to permit simultaneous support of applications conforming to different releases of this specification. I. Introductory Elements Table of Contents 1. Scope 1.1. General 1.2. Module Specific Scope 2. References 2.1. Normative References 2.2. Informative References/Bibliography 3. Requirements 3.1. Relevant Libraries 3.2. LSB Implementation Conformance 3.3. LSB Application Conformance 4. Definitions 5. Terminology 6. Documentation Conventions _________________________________________________________ Chapter 1. Scope 1.1. General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB") describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific supplement ("LSB-arch" or "archLSB") 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. _________________________________________________________ 1.2. 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. References 2.1. Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. Note: Where copies of a document are available on the World Wide Web, a Uniform Resource Locator (URL) is given for informative purposes only. This may point to a more recent copy of the referenced specification, or may be out of date. Reference copies of specifications at the revision level indicated may be found at the Free Standards Group's Reference Specifications site. Table 2-1. Normative References Name Title URL Filesystem Hierarchy Standard Filesystem Hierarchy Standard (FHS) 2.3 http://www.pathname.com/fhs/ IEC 60559/IEEE 754 Floating Point IEC 60559:1989 Binary floating-point arithmetic for microprocessor systems http://www.ieee.org/ Intel® Itanium (TM) Processor-specific Application Binary Interface Intel® Itanium (TM) Processor-specific Application Binary Interface http://refspecs.freestandards.org/elf/IA64-SysV-psABI.pdf ISO C (1999) ISO/IEC 9899: 1999, Programming Languages --C ISO POSIX (2003) ISO/IEC 9945-1:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 1: Base Definitions ISO/IEC 9945-2:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 2: System Interfaces ISO/IEC 9945-3:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 3: Shell and Utilities ISO/IEC 9945-4:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 4: Rationale Including Technical Cor. 1: 2004 http://www.unix.org/version3/ Itanium (TM) Architecture Software Developer's Manual Volume 1 Itanium (TM) Architecture Software Developer's Manual Volume 1: Application Architecture http://refspecs.freestandards.org/IA64-softdevman-vol1.pdf Itanium (TM) Architecture Software Developer's Manual Volume 2 Itanium (TM) Architecture Software Developer's Manual Volume 2: System Architecture http://refspecs.freestandards.org/IA64-softdevman-vol2.pdf Itanium (TM) Architecture Software Developer's Manual Volume 3 Itanium (TM) Architecture Software Developer's Manual Volume 3: Instruction Set Reference http://refspecs.freestandards.org/IA64-softdevman-vol3.pdf Itanium (TM) Architecture Software Developer's Manual Volume 4 IA-64 Processor Reference: Intel® Itanium (TM) Processor Reference Manual for Software Development http://refspecs.freestandards.org/IA64-softdevman-vol4.pdf Itanium (TM) Software Conventions and Runtime Guide Itanium (TM) Software Conventions & Runtime Architecture Guide, September 2000 http://refspecs.freestandards.org/IA64conventions.pdf Large File Support Large File Support http://www.UNIX-systems.org/version2/whatsnew/lfs20mar.html SUSv2 CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606) http://www.opengroup.org/publications/catalog/un.htm SUSv2 Commands and Utilities The Single UNIX® Specification(SUS) Version 2, Commands and Utilities (XCU), Issue 5 (ISBN: 1-85912-191-8, C604) http://www.opengroup.org/publications/catalog/un.htm SVID Issue 3 American Telephone and Telegraph Company, System V Interface Definition, Issue 3 ; Morristown, NJ, UNIX Press, 1989.(ISBN 0201566524) SVID Issue 4 System V Interface Definition,Fourth Edition System V ABI System V Application Binary Interface, Edition 4.1 http://www.caldera.com/developers/devspecs/gabi41.pdf System V ABI Update System V Application Binary Interface - DRAFT - 17 December 2003 http://www.caldera.com/developers/gabi/2003-12-17/contents.htm l X/Open Curses CAE Specification, May 1996, X/Open Curses, Issue 4, Version 2 (ISBN: 1-85912-171-3, C610), plus Corrigendum U018 http://www.opengroup.org/publications/catalog/un.htm _________________________________________________________ 2.2. Informative References/Bibliography In addition, the specifications listed below provide essential background information to implementors of this specification. These references are included for information only. Table 2-2. Other References Name Title URL DWARF Debugging Information Format, Revision 2.0.0 DWARF Debugging Information Format, Revision 2.0.0 (July 27, 1993) http://refspecs.freestandards.org/dwarf/dwarf-2.0.0.pdf DWARF Debugging Information Format, Revision 3.0.0 (Draft) DWARF Debugging Information Format, Revision 3.0.0 (Draft) http://refspecs.freestandards.org/dwarf/ ISO/IEC TR14652 ISO/IEC Technical Report 14652:2002 Specification method for cultural conventions ITU-T V.42 International Telecommunication Union Recommendation V.42 (2002): Error-correcting procedures for DCEs using asynchronous-to-synchronous conversionITUV http://www.itu.int/rec/recommendation.asp?type=folders&lang=e& parent=T-REC-V.42 Li18nux Globalization Specification LI18NUX 2000 Globalization Specification, Version 1.0 with Amendment 4 http://www.li18nux.org/docs/html/LI18NUX-2000-amd4.htm Linux Allocated Device Registry LINUX ALLOCATED DEVICES http://www.lanana.org/docs/device-list/devices.txt PAM Open Software Foundation, Request For Comments: 86.0 , October 1995, V. Samar & R.Schemers (SunSoft) http://www.opengroup.org/tech/rfc/mirror-rfc/rfc86.0.txt RFC 1321: The MD5 Message-Digest Algorithm IETF RFC 1321: The MD5 Message-Digest Algorithm http://www.ietf.org/rfc/rfc1321.txt RFC 1831/1832 RPC & XDR IETF RFC 1831 & 1832 http://www.ietf.org/ RFC 1833: Binding Protocols for ONC RPC Version 2 IETF RFC 1833: Binding Protocols for ONC RPC Version 2 http://www.ietf.org/rfc/rfc1833.txt RFC 1950: ZLIB Compressed Data Format Specication IETF RFC 1950: ZLIB Compressed Data Format Specification http://www.ietf.org/rfc/rfc1950.txt RFC 1951: DEFLATE Compressed Data Format Specification IETF RFC 1951: DEFLATE Compressed Data Format Specification version 1.3 http://www.ietf.org/rfc/rfc1951.txt RFC 1952: GZIP File Format Specification IETF RFC 1952: GZIP file format specification version 4.3 http://www.ietf.org/rfc/rfc1952.txt RFC 2440: OpenPGP Message Format IETF RFC 2440: OpenPGP Message Format http://www.ietf.org/rfc/rfc2440.txt RFC 2821:Simple Mail Transfer Protocol IETF RFC 2821: Simple Mail Transfer Protocol http://www.ietf.org/rfc/rfc2821.txt RFC 2822:Internet Message Format IETF RFC 2822: Internet Message Format http://www.ietf.org/rfc/rfc2822.txt RFC 791:Internet Protocol IETF RFC 791: Internet Protocol Specification http://www.ietf.org/rfc/rfc791.txt RPM Package Format RPM Package Format V3.0 http://www.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format. html zlib Manual zlib 1.2 Manual http://www.gzip.org/zlib/ _________________________________________________________ Chapter 3. Requirements 3.1. 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.3 libgcc_s libgcc_s.so.1 These libraries will be in an implementation-defined directory which the dynamic linker shall search by default. _________________________________________________________ 3.2. LSB Implementation Conformance A conforming implementation is necessarily architecture specific, and must provide the interfaces specified by both the generic LSB Core specification and its relevant architecture specific supplement. Rationale: An implementation must provide at least the interfaces specified in these specifications. It may also provide additional interfaces. A conforming implementation shall satisfy the following requirements: * A processor architecture represents a family of related processors which may not have identical feature sets. The architecture specific supplement to this specification for a given target processor architecture describes a minimum acceptable processor. The implementation shall provide all features of this processor, whether in hardware or through emulation transparent to the application. * The implementation shall be capable of executing compiled applications having the format and using the system interfaces described in this document. * The implementation shall provide libraries containing the interfaces specified by this document, and shall provide a dynamic linking mechanism that allows these interfaces to be attached to applications at runtime. All the interfaces shall behave as specified in this document. * The map of virtual memory provided by the implementation shall conform to the requirements of this document. * The implementation's low-level behavior with respect to function call linkage, system traps, signals, and other such activities shall conform to the formats described in this document. * The implementation shall provide all of the mandatory interfaces in their entirety. * The implementation may provide one or more of the optional interfaces. Each optional interface that is provided shall be provided in its entirety. The product documentation shall state which optional interfaces are provided. * The implementation shall provide all files and utilities specified as part of this document in the format defined here and in other referenced documents. All commands and utilities shall behave as required by this document. The implementation shall also provide all mandatory components of an application's runtime environment that are included or referenced in this document. * The implementation, when provided with standard data formats and values at a named interface, shall provide the behavior defined for those values and data formats at that interface. However, a conforming implementation may consist of components which are separately packaged and/or sold. For example, a vendor of a conforming implementation might sell the hardware, operating system, and windowing system as separately packaged items. * The implementation may provide additional interfaces with different names. It may also provide additional behavior corresponding to data values outside the standard ranges, for standard named interfaces. _________________________________________________________ 3.3. LSB Application Conformance A conforming application is necessarily architecture specific, and must conform to both the generic LSB Core specification and its relevant architecture specific supplement. A conforming application shall satisfy the following requirements: * Its executable files shall be either shell scripts or object files in the format defined for the Object File Format system interface. * Its object files shall participate in dynamic linking as defined in the Program Loading and Linking System interface. * It shall employ only the instructions, traps, and other low-level facilities defined in the Low-Level System interface as being for use by applications. * If it requires any optional interface defined in this document in order to be installed or to execute successfully, the requirement for that optional interface shall be stated in the application's documentation. * It shall not use any interface or data format that is not required to be provided by a conforming implementation, unless: + If such an interface or data format is supplied by another application through direct invocation of that application during execution, that application shall be in turn an LSB conforming application. + The use of that interface or data format, as well as its source, shall be identified in the documentation of the application. * It shall not use any values for a named interface that are reserved for vendor extensions. A strictly conforming application shall not require or use any interface, facility, or implementation-defined extension that is not defined in this document in order to be installed or to execute successfully. _________________________________________________________ Chapter 4. Definitions For the purposes of this document, the following definitions, as specified in the ISO/IEC Directives, Part 2, 2001, 4th Edition, apply: can be able to; there is a possibility of; it is possible to cannot be unable to; there is no possibilty of; it is not possible to may is permitted; is allowed; is permissible need not it is not required that; no...is required shall is to; is required to; it is required that; has to; only...is permitted; it is necessary shall not is not allowed [permitted] [acceptable] [permissible]; is required to be not; is required that...be not; is not to be should it is recommended that; ought to should not it is not recommended that; ought not to _________________________________________________________ Chapter 5. Terminology For the purposes of this document, the following terms apply: archLSB The architectural part of the LSB Specification which describes the specific parts of the interface that are platform specific. The archLSB is complementary to the gLSB. Binary Standard The total set of interfaces that are available to be used in the compiled binary code of a conforming application. gLSB The common part of the LSB Specification that describes those parts of the interface that remain constant across all hardware implementations of the LSB. implementation-defined Describes a value or behavior that is not defined by this document but is selected by an implementor. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence of the value or behavior. An application that relies on such a value or behavior cannot be assured to be portable across conforming implementations. The implementor shall document such a value or behavior so that it can be used correctly by an application. Shell Script A file that is read by an interpreter (e.g., awk). The first line of the shell script includes a reference to its interpreter binary. Source Standard The set of interfaces that are available to be used in the source code of a conforming application. undefined Describes the nature of a value or behavior not defined by this document which results from use of an invalid program construct or invalid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations. unspecified Describes the nature of a value or behavior not specified by this document which results from use of a valid program construct or valid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations. Other terms and definitions used in this document shall have the same meaning as defined in Chapter 3 of the Base Definitions volume of ISO POSIX (2003). _________________________________________________________ Chapter 6. Documentation Conventions Throughout this document, the following typographic conventions are used: function() the name of a function command the name of a command or utility CONSTANT a constant value parameter a parameter variable a variable Throughout this specification, several tables of interfaces are presented. Each entry in these tables has the following format: name the name of the interface (symver) An optional symbol version identifier, if required. [refno] A reference number indexing the table of referenced specifications that follows this table. For example, forkpty(GLIBC_2.0) [SUSv3] refers to the interface named forkpty() with symbol version GLIBC_2.0 that is defined in the SUSv3 reference. Note: Symbol versions are defined in the architecture specific supplements only. II. Executable and Linking Format (ELF) Table of Contents 7. Introduction 8. Low Level System Information 8.1. Machine Interface 8.1.1. Processor Architecture 8.1.2. Data Representation 8.2. Function Calling Sequence 8.2.1. Registers 8.2.2. Floating Point Registers 8.2.3. Stack Frame 8.2.4. Arguments 8.2.5. Return Values 8.3. Operating System Interface 8.3.1. Processor Execution Mode 8.3.2. Exception Interface 8.3.3. Signal Delivery 8.3.4. Debugging Support 8.3.5. Process Startup 8.4. Process Initialization 8.4.1. Special Registers 8.4.2. Process Stack (on entry) 8.4.3. Auxiliary Vector 8.4.4. Environment 8.5. Coding Examples 8.5.1. Introduction 8.5.2. Code Model Overview/Architecture Constraints 8.5.3. Position-Independent Function Prologue 8.5.4. Data Objects 8.5.5. Function Calls 8.5.6. Branching 8.6. C Stack Frame 8.6.1. Variable Argument List 8.6.2. Dynamic Allocation of Stack Space 8.7. Debug Information 9. Object Format 9.1. Introduction 9.2. ELF Header 9.2.1. Machine Information 9.3. Sections 9.3.1. Special Sections 9.3.2. Linux Special Sections 9.3.3. Section Types 9.3.4. Section Attribute Flags 9.3.5. Special Section Types 9.4. Symbol Table 9.5. Relocation 9.5.1. Relocation Types 10. Program Loading and Dynamic Linking 10.1. Introduction 10.2. Program Header 10.2.1. Types 10.2.2. Flags 10.3. Program Loading 10.4. Dynamic Linking 10.4.1. Dynamic Entries 10.4.2. Global Offset Table 10.4.3. Shared Object Dependencies 10.4.4. Function Addresses 10.4.5. Procedure Linkage Table 10.4.6. Initialization and Termination Functions _________________________________________________________ Chapter 7. Introduction Executable and Linking Format (ELF) defines the object format for compiled applications. This specification supplements the information found in System V ABI Update and Intel® Itanium (TM) Processor-specific Application Binary Interface, and is intended to document additions made since the publication of that document. _________________________________________________________ Chapter 8. Low Level System Information 8.1. Machine Interface 8.1.1. Processor Architecture The Itanium(TM) Architecture is specified by the following documents * Itanium (TM) Architecture Software Developer's Manual Volume 1 * Itanium (TM) Architecture Software Developer's Manual Volume 2 * Itanium (TM) Architecture Software Developer's Manual Volume 3 * Itanium (TM) Architecture Software Developer's Manual Volume 4 * Itanium (TM) Software Conventions and Runtime Guide * Intel® Itanium (TM) Processor-specific Application Binary Interface Only the features of the Itanium(TM) processor instruction set may be assumed to be present. An application should determine if any additional instruction set features are available before using those additional features. If a feature is not present, then the application may not use it. Conforming applications may use only instructions which do not require elevated privileges. Conforming applications shall not invoke the implementations underlying system call interface directly. The interfaces in the implementation base libraries shall be used instead. Rationale: Implementation-supplied base libraries may use the system call interface but applications must not assume any particular operating system or kernel version is present. There are some features of the Itanium(TM) 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 (TM) Processor-specific Application Binary Interface for further information. _________________________________________________________ 8.1.2. Data Representation The following sections, in conjunction with section 4 of Itanium (TM) Software Conventions and Runtime Guide, define the size, alignment requirements, and hardware representation of the standard C data types. 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. _________________________________________________________ 8.1.2.1. Byte Ordering LSB-conforming applications shall use little-endian byte ordering. LSB-conforming implementations may support big-endian applications. _________________________________________________________ 8.1.2.2. Fundamental Types Table 8-1 describes how fundemental C language data types shall be represented: Table 8-1. Scalar Types Type C sizeof Alignment (bytes) Hardware Representation Integral _Bool 1 1 byte (sign unspecified) char 1 1 signed byte signed char unsigned char signed byte short 2 2 signed halfword signed short unsigned short unsigned halfword int 4 4 signed word signed int unsigned int unsigned word long 8 8 signed doubleword signed long unsigned long unsigned doubleword long long 8 8 signed doubleword signed long long unsigned long long unsigned doubleword Pointer any-type * 8 8 unsigned doubleword any-type (*)() Floating-Point float 4 4 IEEE Single-precision double 8 8 IEEE Double-precision long double 16 16 IEEE Double-extended A null pointer (for all types) shall have the value zero. _________________________________________________________ 8.1.2.3. 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. struct { char c; } Byte aligned, sizeof is 1 Offset Byte 0 0 c^0 Figure 8-1. Structure Smaller Than A Word 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 8-2. No 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 Figure 8-3. Internal and Tail Padding _________________________________________________________ 8.1.2.4. 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. Bit-field Type Width w Range signed char char unsigned char 1 to 8 -2^w-1 to 2^w-1-1 0 to 2^w-1 0 to 2^w-1 signed short short unsigned short 1 to 16 -2^w-1 to 2^w-1-1 0 to 2^w-1 0 to 2^w-1 signed int int unsigned int 1 to 32 -2^w-1 to 2^w-1-1 0 to 2^w-1 0 to 2^w-1 signed long long unsigned long 1 to 64 -2^w-1 to 2^w-1-1 0 to 2^w-1 0 to 2^w-1 Figure 8-4. Bit-Field Ranges _________________________________________________________ 8.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 (TM) Software Conventions and Runtime Guide. _________________________________________________________ 8.2.1. Registers The CPU general and other registers are as defined in the Itanium (TM) Architecture Software Developer's Manual Volume 1 Section 3.1. _________________________________________________________ 8.2.2. Floating Point Registers The floating point registers are as defined in the Itanium (TM) Architecture Software Developer's Manual Volume 1 Section 3.1. _________________________________________________________ 8.2.3. Stack Frame The stackframe layout is as described in the Itanium (TM) Software Conventions and Runtime Guide Chapter 8.4. _________________________________________________________ 8.2.4. Arguments 8.2.4.1. Introduction The procedure parameter passing mechanism is as described in the Itanium (TM) Software Conventions and Runtime Guide Chapter 8.5. The following subsections provide additional information. _________________________________________________________ 8.2.4.2. Integral/Pointer See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.5. _________________________________________________________ 8.2.4.3. Floating Point See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.5. _________________________________________________________ 8.2.4.4. Struct and Union Point See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.5. _________________________________________________________ 8.2.4.5. Variable Arguments See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.5.4. _________________________________________________________ 8.2.5. Return Values 8.2.5.1. Introduction Values are returned from functions as described in Itanium (TM) Software Conventions and Runtime Guide Chapter 8.6, and as further described here. _________________________________________________________ 8.2.5.2. Void Functions that return no value (void functions) are not required to put any particular value in any general register. _________________________________________________________ 8.2.5.3. Integral/Pointer See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.6. _________________________________________________________ 8.2.5.4. Floating Point See Itanium (TM) Software Conventions and Runtime Guide Chapter 8.6. _________________________________________________________ 8.2.5.5. Struct and Union See Itanium (TM) Software Conventions and Runtime 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. _________________________________________________________ 8.3. Operating System Interface LSB-conforming applications shall use the Operating System Interfaces as defined in Chapter 3 of the Intel® Itanium (TM) Processor-specific Application Binary Interface. _________________________________________________________ 8.3.1. 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. _________________________________________________________ 8.3.2. Exception Interface 8.3.2.1. Introduction LSB-conforming implementations shall support the exception interface as specified in Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.1. _________________________________________________________ 8.3.2.2. Hardware Exception Types See Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.1. _________________________________________________________ 8.3.2.3. Software Trap Types See Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.1. _________________________________________________________ 8.3.3. Signal Delivery LSB-conforming systems shall deliver signals as specified in Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.2. _________________________________________________________ 8.3.3.1. Signal Handler Interface The signal handler interface shall be as specified in Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.3. _________________________________________________________ 8.3.4. Debugging Support The LSB does not specify debugging information. _________________________________________________________ 8.3.5. Process Startup LSB-conforming systems shall initialize processes as specified in Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.5. _________________________________________________________ 8.4. Process Initialization LSB-conforming applications shall use the Process Startup as defined in Section 3.3.5 of the Intel® Itanium (TM) Processor-specific Application Binary Interface. _________________________________________________________ 8.4.1. Special Registers Intel® Itanium (TM) Processor-specific Application Binary Interface, section 3.3.5, defines required register initializations for process startup. _________________________________________________________ 8.4.2. Process Stack (on entry) As defined in Intel® Itanium (TM) 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. _________________________________________________________ 8.4.3. 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. _________________________________________________________ 8.4.4. 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 POSIX (2003), Section exec()). _________________________________________________________ 8.5. Coding Examples 8.5.1. Introduction 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 (TM) Software Conventions and Runtime Guide, Chapter 9. _________________________________________________________ 8.5.2. Code Model Overview/Architecture Constraints As defined in Intel® Itanium (TM) Processor-specific Application Binary Interface, relocatable files, executable files, and shared object files that are supplied as part of an application shall use Position Independent Code, as described in Itanium (TM) Software Conventions and Runtime Guide, Chapter 12. _________________________________________________________ 8.5.3. Position-Independent Function Prologue See Itanium (TM) Software Conventions and Runtime Guide, Chapter 8.4. _________________________________________________________ 8.5.4. Data Objects See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.4, and Itanium (TM) Software Conventions and Runtime Guide, Chapter 12.3. _________________________________________________________ 8.5.4.1. Absolute Load & Store Conforming applications shall not use absolute addressing. _________________________________________________________ 8.5.4.2. Position Relative Load & Store See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.4. _________________________________________________________ 8.5.5. Function Calls See Itanium (TM) Software Conventions and Runtime Guide, Chapter 8.4. Four types of procedure call are defined in Itanium (TM) Software Conventions and Runtime 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 (TM) Software Conventions and Runtime Guide, Chapter 8.3. _________________________________________________________ 8.5.5.1. Absolute Direct Function Call Conforming applications shall not use absolute addressing. _________________________________________________________ 8.5.5.2. Absolute Indirect Function Call Conforming applications shall not use absolute addressing. _________________________________________________________ 8.5.5.3. Position-Independent Direct Function Call See Itanium (TM) Software Conventions and Runtime Guide, Chapter 8.4.1. _________________________________________________________ 8.5.5.4. Position-Independent Indirect Function Call See Itanium (TM) Software Conventions and Runtime Guide, Chapter 8.4.2. _________________________________________________________ 8.5.6. Branching Branching is described in Itanium (TM) Architecture Software Developer's Manual Volume 4, Chapter 4.5. _________________________________________________________ 8.5.6.1. Branch Instruction See Itanium (TM) Architecture Software Developer's Manual Volume 4, Chapter 4.5. _________________________________________________________ 8.5.6.2. Absolute switch() code Conforming applications shall not use absolute addressing. _________________________________________________________ 8.5.6.3. 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 (TM) Software Conventions and Runtime Guide, Chapter 9.1.7. _________________________________________________________ 8.6. C Stack Frame 8.6.1. Variable Argument List See Itanium (TM) Software Conventions and Runtime Guide, Chapter 8.5.2, and 8.5.4. _________________________________________________________ 8.6.2. Dynamic Allocation of Stack Space The C library alloca() function should be used to dynamically allocate stack space. _________________________________________________________ 8.7. Debug Information The LSB does not currently specify the format of Debug information. _________________________________________________________ Chapter 9. Object Format 9.1. Introduction LSB-conforming implementations shall support an object file , called Executable and Linking Format (ELF) as defined by the System V ABI, Intel® Itanium (TM) Processor-specific Application Binary Interface and as supplemented by the Linux Standard Base Specification and this document. _________________________________________________________ 9.2. ELF Header 9.2.1. Machine Information LSB-conforming applications shall use the Machine Information as defined in Intel® Itanium (TM) 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. _________________________________________________________ 9.2.1.1. 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. _________________________________________________________ 9.2.1.2. 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. _________________________________________________________ 9.2.1.3. OS Identification The OS Identification field e_ident[EI_OSABI] shall contain the value ELFOSABI_NONE. _________________________________________________________ 9.2.1.4. Processor Identification The processor identification value held in e_machine shall contain the value EM_IA_64. _________________________________________________________ 9.2.1.5. Processor Specific Flags The flags field e_flags shall be as described in Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 4.1.1.6. The following additional processor-specific flags are defined: Table 9-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. _________________________________________________________ 9.3. Sections The Itanium(TM) architecture defines two processor-specific section types, as described in Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 4. _________________________________________________________ 9.3.1. Special Sections The following sections are defined in the Intel® Itanium (TM) Processor-specific Application Binary Interface. Table 9-2. 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+SHF_IA_64_SHORT .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. _________________________________________________________ 9.3.2. Linux Special Sections The following Linux IA-64 specific sections are defined here. Table 9-3. 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. _________________________________________________________ 9.3.3. Section Types Section Types are described in the Intel® Itanium (TM) 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. _________________________________________________________ 9.3.4. Section Attribute Flags LSB-conforming implementations shall support the section attribute flags specified in Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 4.2.2. _________________________________________________________ 9.3.5. Special Section Types The special section types SHT_IA64_EXT and SHT_IA64_UNWIND are defined in Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 4.2.1. _________________________________________________________ 9.4. 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. _________________________________________________________ 9.5. Relocation 9.5.1. Relocation Types LSB-conforming systems shall support the relocation types described in Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 4.3. _________________________________________________________ Chapter 10. Program Loading and Dynamic Linking 10.1. Introduction LSB-conforming implementations shall support the object file information and system actions that create running programs as specified in the System V ABI, Intel® Itanium (TM) Processor-specific Application Binary Interface and as supplemented by the Linux Standard Base Specification and this document. _________________________________________________________ 10.2. Program Header The program header shall be as defined in the Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5. _________________________________________________________ 10.2.1. Types See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.1. _________________________________________________________ 10.2.2. Flags See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.1. _________________________________________________________ 10.3. Program Loading See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.2. _________________________________________________________ 10.4. Dynamic Linking See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3. _________________________________________________________ 10.4.1. Dynamic Entries 10.4.1.1. ELF Dynamic Entries The following dynamic entries are defined in the Intel® Itanium (TM) 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 _________________________________________________________ 10.4.1.2. Additional Dynamic Entries The following dynamic entries are defined here. DT_RELACOUNT The number of relative relocations in .rela.dyn _________________________________________________________ 10.4.2. Global Offset Table See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.4. _________________________________________________________ 10.4.3. Shared Object Dependencies See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.3. _________________________________________________________ 10.4.4. Function Addresses See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.5. _________________________________________________________ 10.4.5. Procedure Linkage Table See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.6. _________________________________________________________ 10.4.6. Initialization and Termination Functions See Intel® Itanium (TM) Processor-specific Application Binary Interface, Chapter 5.3.7. III. Base Libraries Table of Contents 11. Libraries 11.1. Program Interpreter/Dynamic Linker 11.2. Interfaces for libc 11.2.1. RPC 11.2.2. System Calls 11.2.3. Standard I/O 11.2.4. Signal Handling 11.2.5. Localization Functions 11.2.6. Socket Interface 11.2.7. Wide Characters 11.2.8. String Functions 11.2.9. IPC Functions 11.2.10. Regular Expressions 11.2.11. Character Type Functions 11.2.12. Time Manipulation 11.2.13. Terminal Interface Functions 11.2.14. System Database Interface 11.2.15. Language Support 11.2.16. Large File Support 11.2.17. Standard Library 11.3. Data Definitions for libc 11.3.1. arpa/inet.h 11.3.2. assert.h 11.3.3. ctype.h 11.3.4. dirent.h 11.3.5. err.h 11.3.6. errno.h 11.3.7. fcntl.h 11.3.8. fmtmsg.h 11.3.9. fnmatch.h 11.3.10. ftw.h 11.3.11. getopt.h 11.3.12. glob.h 11.3.13. grp.h 11.3.14. iconv.h 11.3.15. inttypes.h 11.3.16. langinfo.h 11.3.17. libgen.h 11.3.18. libintl.h 11.3.19. limits.h 11.3.20. locale.h 11.3.21. monetary.h 11.3.22. net/if.h 11.3.23. netdb.h 11.3.24. netinet/in.h 11.3.25. netinet/ip.h 11.3.26. netinet/tcp.h 11.3.27. netinet/udp.h 11.3.28. nl_types.h 11.3.29. poll.h 11.3.30. pty.h 11.3.31. pwd.h 11.3.32. regex.h 11.3.33. rpc/auth.h 11.3.34. rpc/clnt.h 11.3.35. rpc/pmap_clnt.h 11.3.36. rpc/rpc_msg.h 11.3.37. rpc/svc.h 11.3.38. rpc/types.h 11.3.39. rpc/xdr.h 11.3.40. sched.h 11.3.41. search.h 11.3.42. setjmp.h 11.3.43. signal.h 11.3.44. stddef.h 11.3.45. stdio.h 11.3.46. stdlib.h 11.3.47. string.h 11.3.48. sys/file.h 11.3.49. sys/ioctl.h 11.3.50. sys/ipc.h 11.3.51. sys/mman.h 11.3.52. sys/msg.h 11.3.53. sys/param.h 11.3.54. sys/poll.h 11.3.55. sys/resource.h 11.3.56. sys/sem.h 11.3.57. sys/shm.h 11.3.58. sys/socket.h 11.3.59. sys/stat.h 11.3.60. sys/statvfs.h 11.3.61. sys/time.h 11.3.62. sys/timeb.h 11.3.63. sys/times.h 11.3.64. sys/types.h 11.3.65. sys/uio.h 11.3.66. sys/un.h 11.3.67. sys/utsname.h 11.3.68. sys/wait.h 11.3.69. syslog.h 11.3.70. termios.h 11.3.71. time.h 11.3.72. ucontext.h 11.3.73. ulimit.h 11.3.74. unistd.h 11.3.75. utime.h 11.3.76. utmp.h 11.3.77. utmpx.h 11.3.78. wchar.h 11.3.79. wctype.h 11.3.80. wordexp.h 11.4. Interfaces for libm 11.4.1. Math 11.5. Data Definitions for libm 11.5.1. complex.h 11.5.2. fenv.h 11.5.3. math.h 11.6. Interfaces for libpthread 11.6.1. Realtime Threads 11.6.2. Advanced Realtime Threads 11.6.3. Posix Threads 11.6.4. Thread aware versions of libc interfaces 11.7. Data Definitions for libpthread 11.7.1. pthread.h 11.7.2. semaphore.h 11.8. Interfaces for libgcc_s 11.8.1. Unwind Library 11.9. Data Definitions for libgcc_s 11.9.1. unwind.h 11.10. Interface Definitions for libgcc_s _Unwind_DeleteException -- private C++ error handling method _Unwind_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 11.11. Interfaces for libdl 11.11.1. Dynamic Loader 11.12. Data Definitions for libdl 11.12.1. dlfcn.h 11.13. Interfaces for libcrypt 11.13.1. Encryption _________________________________________________________ Chapter 11. Libraries An LSB-conforming implementation shall support base libraries which provide interfaces for accessing the operating system, processor and other hardware in the system. Only those interfaces that are unique to the Itanium(TM) platform are defined here. This section should be used in conjunction with the corresponding section in the Linux Standard Base Specification. _________________________________________________________ 11.1. Program Interpreter/Dynamic Linker The Program Interpreter shall be /lib/ld-lsb-ia64.so.3. _________________________________________________________ 11.2. Interfaces for libc Table 11-1 defines the library name and shared object name for the libc library Table 11-1. libc Definition Library: libc SONAME: libc.so.6.1 The behavior of the interfaces in this library is specified by the following specifications: [LFS] Large File Support [LSB] This Specification [SUSv2] SUSv2 [SUSv3] ISO POSIX (2003) [SVID.3] SVID Issue 3 [SVID.4] SVID Issue 4 _________________________________________________________ 11.2.1. RPC _________________________________________________________ 11.2.1.1. Interfaces for RPC An LSB conforming implementation shall provide the architecture specific functions for RPC specified in Table 11-2, with the full mandatory functionality as described in the referenced underlying specification. Table 11-2. libc - RPC Function Interfaces authnone_create(GLIBC_2.2) [SVID.4] clnt_create(GLIBC_2.2) [SVID.4] clnt_pcreateerror(GLIBC_2.2) [SVID.4] clnt_perrno(GLIBC_2.2) [SVID.4] clnt_perror(GLIBC_2.2) [SVID.4] clnt_spcreateerror(GLIBC_2.2) [SVID.4] clnt_sperrno(GLIBC_2.2) [SVID.4] clnt_sperror(GLIBC_2.2) [SVID.4] key_decryptsession(GLIBC_2.2) [SVID.3] pmap_getport(GLIBC_2.2) [LSB] pmap_set(GLIBC_2.2) [LSB] pmap_unset(GLIBC_2.2) [LSB] svc_getreqset(GLIBC_2.2) [SVID.3] svc_register(GLIBC_2.2) [LSB] svc_run(GLIBC_2.2) [LSB] svc_sendreply(GLIBC_2.2) [LSB] svcerr_auth(GLIBC_2.2) [SVID.3] svcerr_decode(GLIBC_2.2) [SVID.3] svcerr_noproc(GLIBC_2.2) [SVID.3] svcerr_noprog(GLIBC_2.2) [SVID.3] svcerr_progvers(GLIBC_2.2) [SVID.3] svcerr_systemerr(GLIBC_2.2) [SVID.3] svcerr_weakauth(GLIBC_2.2) [SVID.3] svctcp_create(GLIBC_2.2) [LSB] svcudp_create(GLIBC_2.2) [LSB] xdr_accepted_reply(GLIBC_2.2) [SVID.3] xdr_array(GLIBC_2.2) [SVID.3] xdr_bool(GLIBC_2.2) [SVID.3] xdr_bytes(GLIBC_2.2) [SVID.3] xdr_callhdr(GLIBC_2.2) [SVID.3] xdr_callmsg(GLIBC_2.2) [SVID.3] xdr_char(GLIBC_2.2) [SVID.3] xdr_double(GLIBC_2.2) [SVID.3] xdr_enum(GLIBC_2.2) [SVID.3] xdr_float(GLIBC_2.2) [SVID.3] xdr_free(GLIBC_2.2) [SVID.3] xdr_int(GLIBC_2.2) [SVID.3] xdr_long(GLIBC_2.2) [SVID.3] xdr_opaque(GLIBC_2.2) [SVID.3] xdr_opaque_auth(GLIBC_2.2) [SVID.3] xdr_pointer(GLIBC_2.2) [SVID.3] xdr_reference(GLIBC_2.2) [SVID.3] xdr_rejected_reply(GLIBC_2.2) [SVID.3] xdr_replymsg(GLIBC_2.2) [SVID.3] xdr_short(GLIBC_2.2) [SVID.3] xdr_string(GLIBC_2.2) [SVID.3] xdr_u_char(GLIBC_2.2) [SVID.3] xdr_u_int(GLIBC_2.2) [LSB] xdr_u_long(GLIBC_2.2) [SVID.3] xdr_u_short(GLIBC_2.2) [SVID.3] xdr_union(GLIBC_2.2) [SVID.3] xdr_vector(GLIBC_2.2) [SVID.3] xdr_void(GLIBC_2.2) [SVID.3] xdr_wrapstring(GLIBC_2.2) [SVID.3] xdrmem_create(GLIBC_2.2) [SVID.3] xdrrec_create(GLIBC_2.2) [SVID.3] xdrrec_eof(GLIBC_2.2) [SVID.3] _________________________________________________________ 11.2.2. System Calls _________________________________________________________ 11.2.2.1. Interfaces for System Calls An LSB conforming implementation shall provide the architecture specific functions for System Calls specified in Table 11-3, with the full mandatory functionality as described in the referenced underlying specification. Table 11-3. libc - System Calls Function Interfaces __fxstat(GLIBC_2.2) [LSB] __getpgid(GLIBC_2.2) [LSB] __lxstat(GLIBC_2.2) [LSB] __xmknod(GLIBC_2.2) [LSB] __xstat(GLIBC_2.2) [LSB] access(GLIBC_2.2) [SUSv3] acct(GLIBC_2.2) [LSB] alarm(GLIBC_2.2) [SUSv3] brk(GLIBC_2.2) [SUSv2] chdir(GLIBC_2.2) [SUSv3] chmod(GLIBC_2.2) [SUSv3] chown(GLIBC_2.2) [SUSv3] chroot(GLIBC_2.2) [SUSv2] clock(GLIBC_2.2) [SUSv3] close(GLIBC_2.2) [SUSv3] closedir(GLIBC_2.2) [SUSv3] creat(GLIBC_2.2) [SUSv3] dup(GLIBC_2.2) [SUSv3] dup2(GLIBC_2.2) [SUSv3] execl(GLIBC_2.2) [SUSv3] execle(GLIBC_2.2) [SUSv3] execlp(GLIBC_2.2) [SUSv3] execv(GLIBC_2.2) [SUSv3] execve(GLIBC_2.2) [SUSv3] execvp(GLIBC_2.2) [SUSv3] exit(GLIBC_2.2) [SUSv3] fchdir(GLIBC_2.2) [SUSv3] fchmod(GLIBC_2.2) [SUSv3] fchown(GLIBC_2.2) [SUSv3] fcntl(GLIBC_2.2) [LSB] fdatasync(GLIBC_2.2) [SUSv3] flock(GLIBC_2.2) [LSB] fork(GLIBC_2.2) [SUSv3] fstatvfs(GLIBC_2.2) [SUSv3] fsync(GLIBC_2.2) [SUSv3] ftime(GLIBC_2.2) [SUSv3] ftruncate(GLIBC_2.2) [SUSv3] getcontext(GLIBC_2.2) [SUSv3] getegid(GLIBC_2.2) [SUSv3] geteuid(GLIBC_2.2) [SUSv3] getgid(GLIBC_2.2) [SUSv3] getgroups(GLIBC_2.2) [SUSv3] getitimer(GLIBC_2.2) [SUSv3] getloadavg(GLIBC_2.2) [LSB] getpagesize(GLIBC_2.2) [SUSv2] getpgid(GLIBC_2.2) [SUSv3] getpgrp(GLIBC_2.2) [SUSv3] getpid(GLIBC_2.2) [SUSv3] getppid(GLIBC_2.2) [SUSv3] getpriority(GLIBC_2.2) [SUSv3] getrlimit(GLIBC_2.2) [SUSv3] getrusage(GLIBC_2.2) [SUSv3] getsid(GLIBC_2.2) [SUSv3] getuid(GLIBC_2.2) [SUSv3] getwd(GLIBC_2.2) [SUSv3] initgroups(GLIBC_2.2) [LSB] ioctl(GLIBC_2.2) [LSB] kill(GLIBC_2.2) [LSB] killpg(GLIBC_2.2) [SUSv3] lchown(GLIBC_2.2) [SUSv3] link(GLIBC_2.2) [LSB] lockf(GLIBC_2.2) [SUSv3] lseek(GLIBC_2.2) [SUSv3] mkdir(GLIBC_2.2) [SUSv3] mkfifo(GLIBC_2.2) [SUSv3] mlock(GLIBC_2.2) [SUSv3] mlockall(GLIBC_2.2) [SUSv3] mmap(GLIBC_2.2) [SUSv3] mprotect(GLIBC_2.2) [SUSv3] msync(GLIBC_2.2) [SUSv3] munlock(GLIBC_2.2) [SUSv3] munlockall(GLIBC_2.2) [SUSv3] munmap(GLIBC_2.2) [SUSv3] nanosleep(GLIBC_2.2) [SUSv3] nice(GLIBC_2.2) [SUSv3] open(GLIBC_2.2) [SUSv3] opendir(GLIBC_2.2) [SUSv3] pathconf(GLIBC_2.2) [SUSv3] pause(GLIBC_2.2) [SUSv3] pipe(GLIBC_2.2) [SUSv3] poll(GLIBC_2.2) [SUSv3] read(GLIBC_2.2) [SUSv3] readdir(GLIBC_2.2) [SUSv3] readdir_r(GLIBC_2.2) [SUSv3] readlink(GLIBC_2.2) [SUSv3] readv(GLIBC_2.2) [SUSv3] rename(GLIBC_2.2) [SUSv3] rmdir(GLIBC_2.2) [SUSv3] sbrk(GLIBC_2.2) [SUSv2] sched_get_priority_max(GLIBC_2.2) [SUSv3] sched_get_priority_min(GLIBC_2.2) [SUSv3] sched_getparam(GLIBC_2.2) [SUSv3] sched_getscheduler(GLIBC_2.2) [SUSv3] sched_rr_get_interval(GLIBC_2.2) [SUSv3] sched_setparam(GLIBC_2.2) [SUSv3] sched_setscheduler(GLIBC_2.2) [SUSv3] sched_yield(GLIBC_2.2) [SUSv3] select(GLIBC_2.2) [SUSv3] setcontext(GLIBC_2.2) [SUSv3] setegid(GLIBC_2.2) [SUSv3] seteuid(GLIBC_2.2) [SUSv3] setgid(GLIBC_2.2) [SUSv3] setitimer(GLIBC_2.2) [SUSv3] setpgid(GLIBC_2.2) [SUSv3] setpgrp(GLIBC_2.2) [SUSv3] setpriority(GLIBC_2.2) [SUSv3] setregid(GLIBC_2.2) [SUSv3] setreuid(GLIBC_2.2) [SUSv3] setrlimit(GLIBC_2.2) [SUSv3] setrlimit64(GLIBC_2.2) [LFS] setsid(GLIBC_2.2) [SUSv3] setuid(GLIBC_2.2) [SUSv3] sleep(GLIBC_2.2) [SUSv3] statvfs(GLIBC_2.2) [SUSv3] stime(GLIBC_2.2) [LSB] symlink(GLIBC_2.2) [SUSv3] sync(GLIBC_2.2) [SUSv3] sysconf(GLIBC_2.2) [SUSv3] time(GLIBC_2.2) [SUSv3] times(GLIBC_2.2) [SUSv3] truncate(GLIBC_2.2) [SUSv3] ulimit(GLIBC_2.2) [SUSv3] umask(GLIBC_2.2) [SUSv3] uname(GLIBC_2.2) [SUSv3] unlink(GLIBC_2.2) [LSB] utime(GLIBC_2.2) [SUSv3] utimes(GLIBC_2.2) [SUSv3] vfork(GLIBC_2.2) [SUSv3] wait(GLIBC_2.2) [SUSv3] wait4(GLIBC_2.2) [LSB] waitpid(GLIBC_2.2) [LSB] write(GLIBC_2.2) [SUSv3] writev(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.3. Standard I/O _________________________________________________________ 11.2.3.1. Interfaces for Standard I/O An LSB conforming implementation shall provide the architecture specific functions for Standard I/O specified in Table 11-4, with the full mandatory functionality as described in the referenced underlying specification. Table 11-4. libc - Standard I/O Function Interfaces _IO_feof(GLIBC_2.2) [LSB] _IO_getc(GLIBC_2.2) [LSB] _IO_putc(GLIBC_2.2) [LSB] _IO_puts(GLIBC_2.2) [LSB] asprintf(GLIBC_2.2) [LSB] clearerr(GLIBC_2.2) [SUSv3] ctermid(GLIBC_2.2) [SUSv3] fclose(GLIBC_2.2) [SUSv3] fdopen(GLIBC_2.2) [SUSv3] feof(GLIBC_2.2) [SUSv3] ferror(GLIBC_2.2) [SUSv3] fflush(GLIBC_2.2) [SUSv3] fflush_unlocked(GLIBC_2.2) [LSB] fgetc(GLIBC_2.2) [SUSv3] fgetpos(GLIBC_2.2) [SUSv3] fgets(GLIBC_2.2) [SUSv3] fgetwc_unlocked(GLIBC_2.2) [LSB] fileno(GLIBC_2.2) [SUSv3] flockfile(GLIBC_2.2) [SUSv3] fopen(GLIBC_2.2) [SUSv3] fprintf(GLIBC_2.2) [SUSv3] fputc(GLIBC_2.2) [SUSv3] fputs(GLIBC_2.2) [SUSv3] fread(GLIBC_2.2) [SUSv3] freopen(GLIBC_2.2) [SUSv3] fscanf(GLIBC_2.2) [LSB] fseek(GLIBC_2.2) [SUSv3] fseeko(GLIBC_2.2) [SUSv3] fsetpos(GLIBC_2.2) [SUSv3] ftell(GLIBC_2.2) [SUSv3] ftello(GLIBC_2.2) [SUSv3] fwrite(GLIBC_2.2) [SUSv3] getc(GLIBC_2.2) [SUSv3] getc_unlocked(GLIBC_2.2) [SUSv3] getchar(GLIBC_2.2) [SUSv3] getchar_unlocked(GLIBC_2.2) [SUSv3] getw(GLIBC_2.2) [SUSv2] pclose(GLIBC_2.2) [SUSv3] popen(GLIBC_2.2) [SUSv3] printf(GLIBC_2.2) [SUSv3] putc(GLIBC_2.2) [SUSv3] putc_unlocked(GLIBC_2.2) [SUSv3] putchar(GLIBC_2.2) [SUSv3] putchar_unlocked(GLIBC_2.2) [SUSv3] puts(GLIBC_2.2) [SUSv3] putw(GLIBC_2.2) [SUSv2] remove(GLIBC_2.2) [SUSv3] rewind(GLIBC_2.2) [SUSv3] rewinddir(GLIBC_2.2) [SUSv3] scanf(GLIBC_2.2) [LSB] seekdir(GLIBC_2.2) [SUSv3] setbuf(GLIBC_2.2) [SUSv3] setbuffer(GLIBC_2.2) [LSB] setvbuf(GLIBC_2.2) [SUSv3] snprintf(GLIBC_2.2) [SUSv3] sprintf(GLIBC_2.2) [SUSv3] sscanf(GLIBC_2.2) [LSB] telldir(GLIBC_2.2) [SUSv3] tempnam(GLIBC_2.2) [SUSv3] ungetc(GLIBC_2.2) [SUSv3] vasprintf(GLIBC_2.2) [LSB] vdprintf(GLIBC_2.2) [LSB] vfprintf(GLIBC_2.2) [SUSv3] vprintf(GLIBC_2.2) [SUSv3] vsnprintf(GLIBC_2.2) [SUSv3] vsprintf(GLIBC_2.2) [SUSv3] An LSB conforming implementation shall provide the architecture specific data interfaces for Standard I/O specified in Table 11-5, with the full mandatory functionality as described in the referenced underlying specification. Table 11-5. libc - Standard I/O Data Interfaces stderr(GLIBC_2.2) [SUSv3] stdin(GLIBC_2.2) [SUSv3] stdout(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.4. Signal Handling _________________________________________________________ 11.2.4.1. Interfaces for Signal Handling An LSB conforming implementation shall provide the architecture specific functions for Signal Handling specified in Table 11-6, with the full mandatory functionality as described in the referenced underlying specification. Table 11-6. libc - Signal Handling Function Interfaces __libc_current_sigrtmax(GLIBC_2.2) [LSB] __libc_current_sigrtmin(GLIBC_2.2) [LSB] __sigsetjmp(GLIBC_2.2) [LSB] __sysv_signal(GLIBC_2.2) [LSB] bsd_signal(GLIBC_2.2) [SUSv3] psignal(GLIBC_2.2) [LSB] raise(GLIBC_2.2) [SUSv3] sigaction(GLIBC_2.2) [SUSv3] sigaddset(GLIBC_2.2) [SUSv3] sigaltstack(GLIBC_2.2) [SUSv3] sigandset(GLIBC_2.2) [LSB] sigdelset(GLIBC_2.2) [SUSv3] sigemptyset(GLIBC_2.2) [SUSv3] sigfillset(GLIBC_2.2) [SUSv3] sighold(GLIBC_2.2) [SUSv3] sigignore(GLIBC_2.2) [SUSv3] siginterrupt(GLIBC_2.2) [SUSv3] sigisemptyset(GLIBC_2.2) [LSB] sigismember(GLIBC_2.2) [SUSv3] siglongjmp(GLIBC_2.2) [SUSv3] signal(GLIBC_2.2) [SUSv3] sigorset(GLIBC_2.2) [LSB] sigpause(GLIBC_2.2) [SUSv3] sigpending(GLIBC_2.2) [SUSv3] sigprocmask(GLIBC_2.2) [SUSv3] sigqueue(GLIBC_2.2) [SUSv3] sigrelse(GLIBC_2.2) [SUSv3] sigreturn(GLIBC_2.2) [LSB] sigset(GLIBC_2.2) [SUSv3] sigsuspend(GLIBC_2.2) [SUSv3] sigtimedwait(GLIBC_2.2) [SUSv3] sigwait(GLIBC_2.2) [SUSv3] sigwaitinfo(GLIBC_2.2) [SUSv3] An LSB conforming implementation shall provide the architecture specific data interfaces for Signal Handling specified in Table 11-7, with the full mandatory functionality as described in the referenced underlying specification. Table 11-7. libc - Signal Handling Data Interfaces _sys_siglist(GLIBC_2.3.3) [LSB] _________________________________________________________ 11.2.5. Localization Functions _________________________________________________________ 11.2.5.1. Interfaces for Localization Functions An LSB conforming implementation shall provide the architecture specific functions for Localization Functions specified in Table 11-8, with the full mandatory functionality as described in the referenced underlying specification. Table 11-8. libc - Localization Functions Function Interfaces bind_textdomain_codeset(GLIBC_2.2) [LSB] bindtextdomain(GLIBC_2.2) [LSB] catclose(GLIBC_2.2) [SUSv3] catgets(GLIBC_2.2) [SUSv3] catopen(GLIBC_2.2) [SUSv3] dcgettext(GLIBC_2.2) [LSB] dcngettext(GLIBC_2.2) [LSB] dgettext(GLIBC_2.2) [LSB] dngettext(GLIBC_2.2) [LSB] gettext(GLIBC_2.2) [LSB] iconv(GLIBC_2.2) [SUSv3] iconv_close(GLIBC_2.2) [SUSv3] iconv_open(GLIBC_2.2) [SUSv3] localeconv(GLIBC_2.2) [SUSv3] ngettext(GLIBC_2.2) [LSB] nl_langinfo(GLIBC_2.2) [SUSv3] setlocale(GLIBC_2.2) [SUSv3] textdomain(GLIBC_2.2) [LSB] An LSB conforming implementation shall provide the architecture specific data interfaces for Localization Functions specified in Table 11-9, with the full mandatory functionality as described in the referenced underlying specification. Table 11-9. libc - Localization Functions Data Interfaces _nl_msg_cat_cntr(GLIBC_2.2) [LSB] _________________________________________________________ 11.2.6. Socket Interface _________________________________________________________ 11.2.6.1. Interfaces for Socket Interface An LSB conforming implementation shall provide the architecture specific functions for Socket Interface specified in Table 11-10, with the full mandatory functionality as described in the referenced underlying specification. Table 11-10. libc - Socket Interface Function Interfaces __h_errno_location(GLIBC_2.2) [LSB] accept(GLIBC_2.2) [SUSv3] bind(GLIBC_2.2) [SUSv3] bindresvport(GLIBC_2.2) [LSB] connect(GLIBC_2.2) [SUSv3] gethostid(GLIBC_2.2) [SUSv3] gethostname(GLIBC_2.2) [SUSv3] getpeername(GLIBC_2.2) [SUSv3] getsockname(GLIBC_2.2) [SUSv3] getsockopt(GLIBC_2.2) [LSB] if_freenameindex(GLIBC_2.2) [SUSv3] if_indextoname(GLIBC_2.2) [SUSv3] if_nameindex(GLIBC_2.2) [SUSv3] if_nametoindex(GLIBC_2.2) [SUSv3] listen(GLIBC_2.2) [SUSv3] recv(GLIBC_2.2) [SUSv3] recvfrom(GLIBC_2.2) [SUSv3] recvmsg(GLIBC_2.2) [SUSv3] send(GLIBC_2.2) [SUSv3] sendmsg(GLIBC_2.2) [SUSv3] sendto(GLIBC_2.2) [SUSv3] setsockopt(GLIBC_2.2) [LSB] shutdown(GLIBC_2.2) [SUSv3] sockatmark(GLIBC_2.2.4) [SUSv3] socket(GLIBC_2.2) [SUSv3] socketpair(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.7. Wide Characters _________________________________________________________ 11.2.7.1. Interfaces for Wide Characters An LSB conforming implementation shall provide the architecture specific functions for Wide Characters specified in Table 11-11, with the full mandatory functionality as described in the referenced underlying specification. Table 11-11. libc - Wide Characters Function Interfaces __wcstod_internal(GLIBC_2.2) [LSB] __wcstof_internal(GLIBC_2.2) [LSB] __wcstol_internal(GLIBC_2.2) [LSB] __wcstold_internal(GLIBC_2.2) [LSB] __wcstoul_internal(GLIBC_2.2) [LSB] btowc(GLIBC_2.2) [SUSv3] fgetwc(GLIBC_2.2) [SUSv3] fgetws(GLIBC_2.2) [SUSv3] fputwc(GLIBC_2.2) [SUSv3] fputws(GLIBC_2.2) [SUSv3] fwide(GLIBC_2.2) [SUSv3] fwprintf(GLIBC_2.2) [SUSv3] fwscanf(GLIBC_2.2) [LSB] getwc(GLIBC_2.2) [SUSv3] getwchar(GLIBC_2.2) [SUSv3] mblen(GLIBC_2.2) [SUSv3] mbrlen(GLIBC_2.2) [SUSv3] mbrtowc(GLIBC_2.2) [SUSv3] mbsinit(GLIBC_2.2) [SUSv3] mbsnrtowcs(GLIBC_2.2) [LSB] mbsrtowcs(GLIBC_2.2) [SUSv3] mbstowcs(GLIBC_2.2) [SUSv3] mbtowc(GLIBC_2.2) [SUSv3] putwc(GLIBC_2.2) [SUSv3] putwchar(GLIBC_2.2) [SUSv3] swprintf(GLIBC_2.2) [SUSv3] swscanf(GLIBC_2.2) [LSB] towctrans(GLIBC_2.2) [SUSv3] towlower(GLIBC_2.2) [SUSv3] towupper(GLIBC_2.2) [SUSv3] ungetwc(GLIBC_2.2) [SUSv3] vfwprintf(GLIBC_2.2) [SUSv3] vfwscanf(GLIBC_2.2) [LSB] vswprintf(GLIBC_2.2) [SUSv3] vswscanf(GLIBC_2.2) [LSB] vwprintf(GLIBC_2.2) [SUSv3] vwscanf(GLIBC_2.2) [LSB] wcpcpy(GLIBC_2.2) [LSB] wcpncpy(GLIBC_2.2) [LSB] wcrtomb(GLIBC_2.2) [SUSv3] wcscasecmp(GLIBC_2.2) [LSB] wcscat(GLIBC_2.2) [SUSv3] wcschr(GLIBC_2.2) [SUSv3] wcscmp(GLIBC_2.2) [SUSv3] wcscoll(GLIBC_2.2) [SUSv3] wcscpy(GLIBC_2.2) [SUSv3] wcscspn(GLIBC_2.2) [SUSv3] wcsdup(GLIBC_2.2) [LSB] wcsftime(GLIBC_2.2) [SUSv3] wcslen(GLIBC_2.2) [SUSv3] wcsncasecmp(GLIBC_2.2) [LSB] wcsncat(GLIBC_2.2) [SUSv3] wcsncmp(GLIBC_2.2) [SUSv3] wcsncpy(GLIBC_2.2) [SUSv3] wcsnlen(GLIBC_2.2) [LSB] wcsnrtombs(GLIBC_2.2) [LSB] wcspbrk(GLIBC_2.2) [SUSv3] wcsrchr(GLIBC_2.2) [SUSv3] wcsrtombs(GLIBC_2.2) [SUSv3] wcsspn(GLIBC_2.2) [SUSv3] wcsstr(GLIBC_2.2) [SUSv3] wcstod(GLIBC_2.2) [SUSv3] wcstof(GLIBC_2.2) [SUSv3] wcstoimax(GLIBC_2.2) [SUSv3] wcstok(GLIBC_2.2) [SUSv3] wcstol(GLIBC_2.2) [SUSv3] wcstold(GLIBC_2.2) [SUSv3] wcstoll(GLIBC_2.2) [SUSv3] wcstombs(GLIBC_2.2) [SUSv3] wcstoq(GLIBC_2.2) [LSB] wcstoul(GLIBC_2.2) [SUSv3] wcstoull(GLIBC_2.2) [SUSv3] wcstoumax(GLIBC_2.2) [SUSv3] wcstouq(GLIBC_2.2) [LSB] wcswcs(GLIBC_2.2) [SUSv3] wcswidth(GLIBC_2.2) [SUSv3] wcsxfrm(GLIBC_2.2) [SUSv3] wctob(GLIBC_2.2) [SUSv3] wctomb(GLIBC_2.2) [SUSv3] wctrans(GLIBC_2.2) [SUSv3] wctype(GLIBC_2.2) [SUSv3] wcwidth(GLIBC_2.2) [SUSv3] wmemchr(GLIBC_2.2) [SUSv3] wmemcmp(GLIBC_2.2) [SUSv3] wmemcpy(GLIBC_2.2) [SUSv3] wmemmove(GLIBC_2.2) [SUSv3] wmemset(GLIBC_2.2) [SUSv3] wprintf(GLIBC_2.2) [SUSv3] wscanf(GLIBC_2.2) [LSB] _________________________________________________________ 11.2.8. String Functions _________________________________________________________ 11.2.8.1. Interfaces for String Functions An LSB conforming implementation shall provide the architecture specific functions for String Functions specified in Table 11-12, with the full mandatory functionality as described in the referenced underlying specification. Table 11-12. libc - String Functions Function Interfaces __mempcpy(GLIBC_2.2) [LSB] __rawmemchr(GLIBC_2.2) [LSB] __stpcpy(GLIBC_2.2) [LSB] __strdup(GLIBC_2.2) [LSB] __strtod_internal(GLIBC_2.2) [LSB] __strtof_internal(GLIBC_2.2) [LSB] __strtok_r(GLIBC_2.2) [LSB] __strtol_internal(GLIBC_2.2) [LSB] __strtold_internal(GLIBC_2.2) [LSB] __strtoll_internal(GLIBC_2.2) [LSB] __strtoul_internal(GLIBC_2.2) [LSB] __strtoull_internal(GLIBC_2.2) [LSB] bcmp(GLIBC_2.2) [SUSv3] bcopy(GLIBC_2.2) [SUSv3] bzero(GLIBC_2.2) [SUSv3] ffs(GLIBC_2.2) [SUSv3] index(GLIBC_2.2) [SUSv3] memccpy(GLIBC_2.2) [SUSv3] memchr(GLIBC_2.2) [SUSv3] memcmp(GLIBC_2.2) [SUSv3] memcpy(GLIBC_2.2) [SUSv3] memmove(GLIBC_2.2) [SUSv3] memrchr(GLIBC_2.2) [LSB] memset(GLIBC_2.2) [SUSv3] rindex(GLIBC_2.2) [SUSv3] stpcpy(GLIBC_2.2) [LSB] stpncpy(GLIBC_2.2) [LSB] strcasecmp(GLIBC_2.2) [SUSv3] strcasestr(GLIBC_2.2) [LSB] strcat(GLIBC_2.2) [SUSv3] strchr(GLIBC_2.2) [SUSv3] strcmp(GLIBC_2.2) [SUSv3] strcoll(GLIBC_2.2) [SUSv3] strcpy(GLIBC_2.2) [SUSv3] strcspn(GLIBC_2.2) [SUSv3] strdup(GLIBC_2.2) [SUSv3] strerror(GLIBC_2.2) [SUSv3] strerror_r(GLIBC_2.2) [LSB] strfmon(GLIBC_2.2) [SUSv3] strftime(GLIBC_2.2) [SUSv3] strlen(GLIBC_2.2) [SUSv3] strncasecmp(GLIBC_2.2) [SUSv3] strncat(GLIBC_2.2) [SUSv3] strncmp(GLIBC_2.2) [SUSv3] strncpy(GLIBC_2.2) [SUSv3] strndup(GLIBC_2.2) [LSB] strnlen(GLIBC_2.2) [LSB] strpbrk(GLIBC_2.2) [SUSv3] strptime(GLIBC_2.2) [LSB] strrchr(GLIBC_2.2) [SUSv3] strsep(GLIBC_2.2) [LSB] strsignal(GLIBC_2.2) [LSB] strspn(GLIBC_2.2) [SUSv3] strstr(GLIBC_2.2) [SUSv3] strtof(GLIBC_2.2) [SUSv3] strtoimax(GLIBC_2.2) [SUSv3] strtok(GLIBC_2.2) [SUSv3] strtok_r(GLIBC_2.2) [SUSv3] strtold(GLIBC_2.2) [SUSv3] strtoll(GLIBC_2.2) [SUSv3] strtoq(GLIBC_2.2) [LSB] strtoull(GLIBC_2.2) [SUSv3] strtoumax(GLIBC_2.2) [SUSv3] strtouq(GLIBC_2.2) [LSB] strxfrm(GLIBC_2.2) [SUSv3] swab(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.9. IPC Functions _________________________________________________________ 11.2.9.1. Interfaces for IPC Functions An LSB conforming implementation shall provide the architecture specific functions for IPC Functions specified in Table 11-13, with the full mandatory functionality as described in the referenced underlying specification. Table 11-13. libc - IPC Functions Function Interfaces ftok(GLIBC_2.2) [SUSv3] msgctl(GLIBC_2.2) [SUSv3] msgget(GLIBC_2.2) [SUSv3] msgrcv(GLIBC_2.2) [SUSv3] msgsnd(GLIBC_2.2) [SUSv3] semctl(GLIBC_2.2) [SUSv3] semget(GLIBC_2.2) [SUSv3] semop(GLIBC_2.2) [SUSv3] shmat(GLIBC_2.2) [SUSv3] shmctl(GLIBC_2.2) [SUSv3] shmdt(GLIBC_2.2) [SUSv3] shmget(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.10. Regular Expressions _________________________________________________________ 11.2.10.1. Interfaces for Regular Expressions An LSB conforming implementation shall provide the architecture specific functions for Regular Expressions specified in Table 11-14, with the full mandatory functionality as described in the referenced underlying specification. Table 11-14. libc - Regular Expressions Function Interfaces regcomp(GLIBC_2.2) [SUSv3] regerror(GLIBC_2.2) [SUSv3] regexec(GLIBC_2.3.4) [LSB] regfree(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.11. Character Type Functions _________________________________________________________ 11.2.11.1. Interfaces for Character Type Functions An LSB conforming implementation shall provide the architecture specific functions for Character Type Functions specified in Table 11-15, with the full mandatory functionality as described in the referenced underlying specification. Table 11-15. libc - Character Type Functions Function Interfaces __ctype_get_mb_cur_max(GLIBC_2.2) [LSB] _tolower(GLIBC_2.2) [SUSv3] _toupper(GLIBC_2.2) [SUSv3] isalnum(GLIBC_2.2) [SUSv3] isalpha(GLIBC_2.2) [SUSv3] isascii(GLIBC_2.2) [SUSv3] iscntrl(GLIBC_2.2) [SUSv3] isdigit(GLIBC_2.2) [SUSv3] isgraph(GLIBC_2.2) [SUSv3] islower(GLIBC_2.2) [SUSv3] isprint(GLIBC_2.2) [SUSv3] ispunct(GLIBC_2.2) [SUSv3] isspace(GLIBC_2.2) [SUSv3] isupper(GLIBC_2.2) [SUSv3] iswalnum(GLIBC_2.2) [SUSv3] iswalpha(GLIBC_2.2) [SUSv3] iswblank(GLIBC_2.2) [SUSv3] iswcntrl(GLIBC_2.2) [SUSv3] iswctype(GLIBC_2.2) [SUSv3] iswdigit(GLIBC_2.2) [SUSv3] iswgraph(GLIBC_2.2) [SUSv3] iswlower(GLIBC_2.2) [SUSv3] iswprint(GLIBC_2.2) [SUSv3] iswpunct(GLIBC_2.2) [SUSv3] iswspace(GLIBC_2.2) [SUSv3] iswupper(GLIBC_2.2) [SUSv3] iswxdigit(GLIBC_2.2) [SUSv3] isxdigit(GLIBC_2.2) [SUSv3] toascii(GLIBC_2.2) [SUSv3] tolower(GLIBC_2.2) [SUSv3] toupper(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.12. Time Manipulation _________________________________________________________ 11.2.12.1. Interfaces for Time Manipulation An LSB conforming implementation shall provide the architecture specific functions for Time Manipulation specified in Table 11-16, with the full mandatory functionality as described in the referenced underlying specification. Table 11-16. libc - Time Manipulation Function Interfaces adjtime(GLIBC_2.2) [LSB] asctime(GLIBC_2.2) [SUSv3] asctime_r(GLIBC_2.2) [SUSv3] ctime(GLIBC_2.2) [SUSv3] ctime_r(GLIBC_2.2) [SUSv3] difftime(GLIBC_2.2) [SUSv3] gmtime(GLIBC_2.2) [SUSv3] gmtime_r(GLIBC_2.2) [SUSv3] localtime(GLIBC_2.2) [SUSv3] localtime_r(GLIBC_2.2) [SUSv3] mktime(GLIBC_2.2) [SUSv3] tzset(GLIBC_2.2) [SUSv3] ualarm(GLIBC_2.2) [SUSv3] An LSB conforming implementation shall provide the architecture specific data interfaces for Time Manipulation specified in Table 11-17, with the full mandatory functionality as described in the referenced underlying specification. Table 11-17. libc - Time Manipulation Data Interfaces __daylight(GLIBC_2.2) [LSB] __timezone(GLIBC_2.2) [LSB] __tzname(GLIBC_2.2) [LSB] daylight(GLIBC_2.2) [SUSv3] timezone(GLIBC_2.2) [SUSv3] tzname(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.13. Terminal Interface Functions _________________________________________________________ 11.2.13.1. Interfaces for Terminal Interface Functions An LSB conforming implementation shall provide the architecture specific functions for Terminal Interface Functions specified in Table 11-18, with the full mandatory functionality as described in the referenced underlying specification. Table 11-18. libc - Terminal Interface Functions Function Interfaces cfgetispeed(GLIBC_2.2) [SUSv3] cfgetospeed(GLIBC_2.2) [SUSv3] cfmakeraw(GLIBC_2.2) [LSB] cfsetispeed(GLIBC_2.2) [SUSv3] cfsetospeed(GLIBC_2.2) [SUSv3] cfsetspeed(GLIBC_2.2) [LSB] tcdrain(GLIBC_2.2) [SUSv3] tcflow(GLIBC_2.2) [SUSv3] tcflush(GLIBC_2.2) [SUSv3] tcgetattr(GLIBC_2.2) [SUSv3] tcgetpgrp(GLIBC_2.2) [SUSv3] tcgetsid(GLIBC_2.2) [SUSv3] tcsendbreak(GLIBC_2.2) [SUSv3] tcsetattr(GLIBC_2.2) [SUSv3] tcsetpgrp(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.2.14. System Database Interface _________________________________________________________ 11.2.14.1. Interfaces for System Database Interface An LSB conforming implementation shall provide the architecture specific functions for System Database Interface specified in Table 11-19, with the full mandatory functionality as described in the referenced underlying specification. Table 11-19. libc - System Database Interface Function Interfaces endgrent(GLIBC_2.2) [SUSv3] endprotoent(GLIBC_2.2) [SUSv3] endpwent(GLIBC_2.2) [SUSv3] endservent(GLIBC_2.2) [SUSv3] endutent(GLIBC_2.2) [SUSv2] endutxent(GLIBC_2.2) [SUSv3] getgrent(GLIBC_2.2) [SUSv3] getgrgid(GLIBC_2.2) [SUSv3] getgrgid_r(GLIBC_2.2) [SUSv3] getgrnam(GLIBC_2.2) [SUSv3] getgrnam_r(GLIBC_2.2) [SUSv3] getgrouplist(GLIBC_2.2.4) [LSB] gethostbyaddr(GLIBC_2.2) [SUSv3] gethostbyname(GLIBC_2.2) [SUSv3] getprotobyname(GLIBC_2.2) [SUSv3] getprotobynumber(GLIBC_2.2) [SUSv3] getprotoent(GLIBC_2.2) [SUSv3] getpwent(GLIBC_2.2) [SUSv3] getpwnam(GLIBC_2.2) [SUSv3] getpwnam_r(GLIBC_2.2) [SUSv3] getpwuid(GLIBC_2.2) [SUSv3] getpwuid_r(GLIBC_2.2) [SUSv3] getservbyname(GLIBC_2.2) [SUSv3] getservbyport(GLIBC_2.2) [SUSv3] getservent(GLIBC_2.2) [SUSv3] getutent(GLIBC_2.2) [LSB] getutent_r(GLIBC_2.2) [LSB] getutxent(GLIBC_2.2) [SUSv3] getutxid(GLIBC_2.2) [SUSv3] getutxline(GLIBC_2.2) [SUSv3] pututxline(GLIBC_2.2) [SUSv3] setgrent(GLIBC_2.2) [SUSv3] setgroups(GLIBC_2.2) [LSB] setprotoent(GLIBC_2.2) [SUSv3] setpwent(GLIBC_2.2) [SUSv3] setservent(GLIBC_2.2) [SUSv3] setutent(GLIBC_2.2) [LSB] setutxent(GLIBC_2.2) [SUSv3] utmpname(GLIBC_2.2) [LSB] _________________________________________________________ 11.2.15. Language Support _________________________________________________________ 11.2.15.1. Interfaces for Language Support An LSB conforming implementation shall provide the architecture specific functions for Language Support specified in Table 11-20, with the full mandatory functionality as described in the referenced underlying specification. Table 11-20. libc - Language Support Function Interfaces __libc_start_main(GLIBC_2.2) [LSB] _________________________________________________________ 11.2.16. Large File Support _________________________________________________________ 11.2.16.1. Interfaces for Large File Support An LSB conforming implementation shall provide the architecture specific functions for Large File Support specified in Table 11-21, with the full mandatory functionality as described in the referenced underlying specification. Table 11-21. libc - Large File Support Function Interfaces __fxstat64(GLIBC_2.2) [LSB] __lxstat64(GLIBC_2.2) [LSB] __xstat64(GLIBC_2.2) [LSB] creat64(GLIBC_2.2) [LFS] fgetpos64(GLIBC_2.2) [LFS] fopen64(GLIBC_2.2) [LFS] freopen64(GLIBC_2.2) [LFS] fseeko64(GLIBC_2.2) [LFS] fsetpos64(GLIBC_2.2) [LFS] fstatvfs64(GLIBC_2.2) [LFS] ftello64(GLIBC_2.2) [LFS] ftruncate64(GLIBC_2.2) [LFS] ftw64(GLIBC_2.2) [LFS] getrlimit64(GLIBC_2.2) [LFS] lockf64(GLIBC_2.2) [LFS] mkstemp64(GLIBC_2.2) [LFS] mmap64(GLIBC_2.2) [LFS] nftw64(GLIBC_2.3.3) [LFS] readdir64(GLIBC_2.2) [LFS] statvfs64(GLIBC_2.2) [LFS] tmpfile64(GLIBC_2.2) [LFS] truncate64(GLIBC_2.2) [LFS] _________________________________________________________ 11.2.17. Standard Library _________________________________________________________ 11.2.17.1. Interfaces for Standard Library An LSB conforming implementation shall provide the architecture specific functions for Standard Library specified in Table 11-22, with the full mandatory functionality as described in the referenced underlying specification. Table 11-22. libc - Standard Library Function Interfaces _Exit(GLIBC_2.2) [SUSv3] __assert_fail(GLIBC_2.2) [LSB] __cxa_atexit(GLIBC_2.2) [LSB] __errno_location(GLIBC_2.2) [LSB] __fpending(GLIBC_2.2) [LSB] __getpagesize(GLIBC_2.2) [LSB] __isinf(GLIBC_2.2) [LSB] __isinff(GLIBC_2.2) [LSB] __isinfl(GLIBC_2.2) [LSB] __isnan(GLIBC_2.2) [LSB] __isnanf(GLIBC_2.2) [LSB] __isnanl(GLIBC_2.2) [LSB] __sysconf(GLIBC_2.2) [LSB] _exit(GLIBC_2.2) [SUSv3] _longjmp(GLIBC_2.2) [SUSv3] _setjmp(GLIBC_2.2) [SUSv3] a64l(GLIBC_2.2) [SUSv3] abort(GLIBC_2.2) [SUSv3] abs(GLIBC_2.2) [SUSv3] atof(GLIBC_2.2) [SUSv3] atoi(GLIBC_2.2) [SUSv3] atol(GLIBC_2.2) [SUSv3] atoll(GLIBC_2.2) [SUSv3] basename(GLIBC_2.2) [SUSv3] bsearch(GLIBC_2.2) [SUSv3] calloc(GLIBC_2.2) [SUSv3] closelog(GLIBC_2.2) [SUSv3] confstr(GLIBC_2.2) [SUSv3] cuserid(GLIBC_2.2) [SUSv2] daemon(GLIBC_2.2) [LSB] dirname(GLIBC_2.2) [SUSv3] div(GLIBC_2.2) [SUSv3] drand48(GLIBC_2.2) [SUSv3] ecvt(GLIBC_2.2) [SUSv3] erand48(GLIBC_2.2) [SUSv3] err(GLIBC_2.2) [LSB] error(GLIBC_2.2) [LSB] errx(GLIBC_2.2) [LSB] fcvt(GLIBC_2.2) [SUSv3] fmtmsg(GLIBC_2.2) [SUSv3] fnmatch(GLIBC_2.2.3) [SUSv3] fpathconf(GLIBC_2.2) [SUSv3] free(GLIBC_2.2) [SUSv3] freeaddrinfo(GLIBC_2.2) [SUSv3] ftrylockfile(GLIBC_2.2) [SUSv3] ftw(GLIBC_2.2) [SUSv3] funlockfile(GLIBC_2.2) [SUSv3] gai_strerror(GLIBC_2.2) [SUSv3] gcvt(GLIBC_2.2) [SUSv3] getaddrinfo(GLIBC_2.2) [SUSv3] getcwd(GLIBC_2.2) [SUSv3] getdate(GLIBC_2.2) [SUSv3] getenv(GLIBC_2.2) [SUSv3] getlogin(GLIBC_2.2) [SUSv3] getlogin_r(GLIBC_2.2) [SUSv3] getnameinfo(GLIBC_2.2) [SUSv3] getopt(GLIBC_2.2) [LSB] getopt_long(GLIBC_2.2) [LSB] getopt_long_only(GLIBC_2.2) [LSB] getsubopt(GLIBC_2.2) [SUSv3] gettimeofday(GLIBC_2.2) [SUSv3] glob(GLIBC_2.2) [SUSv3] glob64(GLIBC_2.2) [LSB] globfree(GLIBC_2.2) [SUSv3] globfree64(GLIBC_2.2) [LSB] grantpt(GLIBC_2.2) [SUSv3] hcreate(GLIBC_2.2) [SUSv3] hdestroy(GLIBC_2.2) [SUSv3] hsearch(GLIBC_2.2) [SUSv3] htonl(GLIBC_2.2) [SUSv3] htons(GLIBC_2.2) [SUSv3] imaxabs(GLIBC_2.2) [SUSv3] imaxdiv(GLIBC_2.2) [SUSv3] inet_addr(GLIBC_2.2) [SUSv3] inet_ntoa(GLIBC_2.2) [SUSv3] inet_ntop(GLIBC_2.2) [SUSv3] inet_pton(GLIBC_2.2) [SUSv3] initstate(GLIBC_2.2) [SUSv3] insque(GLIBC_2.2) [SUSv3] isatty(GLIBC_2.2) [SUSv3] isblank(GLIBC_2.2) [SUSv3] jrand48(GLIBC_2.2) [SUSv3] l64a(GLIBC_2.2) [SUSv3] labs(GLIBC_2.2) [SUSv3] lcong48(GLIBC_2.2) [SUSv3] ldiv(GLIBC_2.2) [SUSv3] lfind(GLIBC_2.2) [SUSv3] llabs(GLIBC_2.2) [SUSv3] lldiv(GLIBC_2.2) [SUSv3] longjmp(GLIBC_2.2) [SUSv3] lrand48(GLIBC_2.2) [SUSv3] lsearch(GLIBC_2.2) [SUSv3] makecontext(GLIBC_2.2) [SUSv3] malloc(GLIBC_2.2) [SUSv3] memmem(GLIBC_2.2) [LSB] mkstemp(GLIBC_2.2) [SUSv3] mktemp(GLIBC_2.2) [SUSv3] mrand48(GLIBC_2.2) [SUSv3] nftw(GLIBC_2.3.3) [SUSv3] nrand48(GLIBC_2.2) [SUSv3] ntohl(GLIBC_2.2) [SUSv3] ntohs(GLIBC_2.2) [SUSv3] openlog(GLIBC_2.2) [SUSv3] perror(GLIBC_2.2) [SUSv3] posix_memalign(GLIBC_2.2) [SUSv3] posix_openpt(GLIBC_2.2.1) [SUSv3] ptsname(GLIBC_2.2) [SUSv3] putenv(GLIBC_2.2) [SUSv3] qsort(GLIBC_2.2) [SUSv3] rand(GLIBC_2.2) [SUSv3] rand_r(GLIBC_2.2) [SUSv3] random(GLIBC_2.2) [SUSv3] realloc(GLIBC_2.2) [SUSv3] realpath(GLIBC_2.3) [SUSv3] remque(GLIBC_2.2) [SUSv3] seed48(GLIBC_2.2) [SUSv3] setenv(GLIBC_2.2) [SUSv3] sethostname(GLIBC_2.2) [LSB] setlogmask(GLIBC_2.2) [SUSv3] setstate(GLIBC_2.2) [SUSv3] srand(GLIBC_2.2) [SUSv3] srand48(GLIBC_2.2) [SUSv3] srandom(GLIBC_2.2) [SUSv3] strtod(GLIBC_2.2) [SUSv3] strtol(GLIBC_2.2) [SUSv3] strtoul(GLIBC_2.2) [SUSv3] swapcontext(GLIBC_2.2) [SUSv3] syslog(GLIBC_2.2) [SUSv3] system(GLIBC_2.2) [LSB] tdelete(GLIBC_2.2) [SUSv3] tfind(GLIBC_2.2) [SUSv3] tmpfile(GLIBC_2.2) [SUSv3] tmpnam(GLIBC_2.2) [SUSv3] tsearch(GLIBC_2.2) [SUSv3] ttyname(GLIBC_2.2) [SUSv3] ttyname_r(GLIBC_2.2) [SUSv3] twalk(GLIBC_2.2) [SUSv3] unlockpt(GLIBC_2.2) [SUSv3] unsetenv(GLIBC_2.2) [SUSv3] usleep(GLIBC_2.2) [SUSv3] verrx(GLIBC_2.2) [LSB] vfscanf(GLIBC_2.2) [LSB] vscanf(GLIBC_2.2) [LSB] vsscanf(GLIBC_2.2) [LSB] vsyslog(GLIBC_2.2) [LSB] warn(GLIBC_2.2) [LSB] warnx(GLIBC_2.2) [LSB] wordexp(GLIBC_2.2.2) [SUSv3] wordfree(GLIBC_2.2) [SUSv3] An LSB conforming implementation shall provide the architecture specific data interfaces for Standard Library specified in Table 11-23, with the full mandatory functionality as described in the referenced underlying specification. Table 11-23. libc - Standard Library Data Interfaces __environ(GLIBC_2.2) [LSB] _environ(GLIBC_2.2) [LSB] _sys_errlist(GLIBC_2.3) [LSB] environ(GLIBC_2.2) [SUSv3] getdate_err(GLIBC_2.2) [SUSv3] optarg(GLIBC_2.2) [SUSv3] opterr(GLIBC_2.2) [SUSv3] optind(GLIBC_2.2) [SUSv3] optopt(GLIBC_2.2) [SUSv3] _________________________________________________________ 11.3. 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. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect. This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications. This specification uses the ISO C (1999) 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. _________________________________________________________ 11.3.1. arpa/inet.h extern uint32_t htonl(uint32_t); extern uint16_t htons(uint16_t); extern in_addr_t inet_addr(const char *); extern char *inet_ntoa(struct in_addr); extern const char *inet_ntop(int, const void *, char *, socklen_t); extern int inet_pton(int, const char *, void *); extern uint32_t ntohl(uint32_t); extern uint16_t ntohs(uint16_t); _________________________________________________________ 11.3.2. assert.h extern void __assert_fail(const char *, const char *, unsigned int, const char *); _________________________________________________________ 11.3.3. ctype.h extern int _tolower(int); extern int _toupper(int); extern int isalnum(int); extern int isalpha(int); extern int isascii(int); extern int iscntrl(int); extern int isdigit(int); extern int isgraph(int); extern int islower(int); extern int isprint(int); extern int ispunct(int); extern int isspace(int); extern int isupper(int); extern int isxdigit(int); extern int toascii(int); extern int tolower(int); extern int toupper(int); extern int isblank(int); extern const unsigned short **__ctype_b_loc(void); extern const int32_t **__ctype_toupper_loc(void); extern const int32_t **__ctype_tolower_loc(void); _________________________________________________________ 11.3.4. dirent.h extern void rewinddir(DIR *); extern void seekdir(DIR *, long int); extern long int telldir(DIR *); extern int closedir(DIR *); extern DIR *opendir(const char *); extern struct dirent *readdir(DIR *); extern struct dirent64 *readdir64(DIR *); extern int readdir_r(DIR *, struct dirent *, struct dirent **); _________________________________________________________ 11.3.5. err.h extern void err(int, const char *, ...); extern void errx(int, const char *, ...); extern void warn(const char *, ...); extern void warnx(const char *, ...); extern void error(int, int, const char *, ...); _________________________________________________________ 11.3.6. errno.h #define EDEADLOCK EDEADLK extern int *__errno_location(void); _________________________________________________________ 11.3.7. fcntl.h #define F_GETLK64 5 #define F_SETLK64 6 #define F_SETLKW64 7 extern int lockf64(int, int, off64_t); extern int fcntl(int, int, ...); _________________________________________________________ 11.3.8. fmtmsg.h extern int fmtmsg(long int, const char *, int, const char *, const char *, const char *); _________________________________________________________ 11.3.9. fnmatch.h extern int fnmatch(const char *, const char *, int); _________________________________________________________ 11.3.10. ftw.h extern int ftw(const char *, __ftw_func_t, int); extern int ftw64(const char *, __ftw64_func_t, int); extern int nftw(const char *, __nftw_func_t, int, int); extern int nftw64(const char *, __nftw64_func_t, int, int); _________________________________________________________ 11.3.11. getopt.h extern int getopt_long(int, char *const, const char *, const struct option *, int *); extern int getopt_long_only(int, char *const, const char *, const struct option *, int *); _________________________________________________________ 11.3.12. glob.h extern int glob(const char *, int, int (*__errfunc) (const char *p1, int p2) , glob_t *); extern int glob64(const char *, int, int (*__errfunc) (const char *p1, int p2) , glob64_t *); extern void globfree(glob_t *); extern void globfree64(glob64_t *); _________________________________________________________ 11.3.13. grp.h extern void endgrent(void); extern struct group *getgrent(void); extern struct group *getgrgid(gid_t); extern struct group *getgrnam(char *); extern int initgroups(const char *, gid_t); extern void setgrent(void); extern int setgroups(size_t, const gid_t *); extern int getgrgid_r(gid_t, struct group *, char *, size_t, struct group **); extern int getgrnam_r(const char *, struct group *, char *, size_t, struct group **); extern int getgrouplist(const char *, gid_t, gid_t *, int *); _________________________________________________________ 11.3.14. iconv.h extern size_t iconv(iconv_t, char **, size_t *, char **, size_t *); extern int iconv_close(iconv_t); extern iconv_t iconv_open(char *, char *); _________________________________________________________ 11.3.15. inttypes.h typedef long int intmax_t; typedef unsigned long int uintmax_t; typedef unsigned long int uintptr_t; typedef unsigned long int uint64_t; extern intmax_t strtoimax(const char *, char **, int); extern uintmax_t strtoumax(const char *, char **, int); extern intmax_t wcstoimax(const wchar_t *, wchar_t * *, int); extern uintmax_t wcstoumax(const wchar_t *, wchar_t * *, int); extern intmax_t imaxabs(intmax_t); extern imaxdiv_t imaxdiv(intmax_t, intmax_t); _________________________________________________________ 11.3.16. langinfo.h extern char *nl_langinfo(nl_item); _________________________________________________________ 11.3.17. libgen.h extern char *basename(const char *); extern char *dirname(char *); _________________________________________________________ 11.3.18. libintl.h extern char *bindtextdomain(const char *, const char *); extern char *dcgettext(const char *, const char *, int); extern char *dgettext(const char *, const char *); extern char *gettext(const char *); extern char *textdomain(const char *); extern char *bind_textdomain_codeset(const char *, const char *); extern char *dcngettext(const char *, const char *, const char *, unsigned long int, int); extern char *dngettext(const char *, const char *, const char *, unsigned long int); extern char *ngettext(const char *, const char *, unsigned long int); _________________________________________________________ 11.3.19. limits.h #define LONG_MAX 0x7FFFFFFFFFFFFFFFL #define ULONG_MAX 0xFFFFFFFFFFFFFFFFUL #define CHAR_MAX SCHAR_MAX #define CHAR_MIN SCHAR_MIN #define PTHREAD_STACK_MIN 196608 _________________________________________________________ 11.3.20. locale.h extern struct lconv *localeconv(void); extern char *setlocale(int, const char *); extern locale_t uselocale(locale_t); extern void freelocale(locale_t); extern locale_t duplocale(locale_t); extern locale_t newlocale(int, const char *, locale_t); _________________________________________________________ 11.3.21. monetary.h extern ssize_t strfmon(char *, size_t, const char *, ...); _________________________________________________________ 11.3.22. net/if.h extern void if_freenameindex(struct if_nameindex *); extern char *if_indextoname(unsigned int, char *); extern struct if_nameindex *if_nameindex(void); extern unsigned int if_nametoindex(const char *); _________________________________________________________ 11.3.23. netdb.h extern void endprotoent(void); extern void endservent(void); extern void freeaddrinfo(struct addrinfo *); extern const char *gai_strerror(int); extern int getaddrinfo(const char *, const char *, const struct addrinfo *, struct addrinfo **); extern struct hostent *gethostbyaddr(const void *, socklen_t, int); extern struct hostent *gethostbyname(const char *); extern struct protoent *getprotobyname(const char *); extern struct protoent *getprotobynumber(int); extern struct protoent *getprotoent(void); extern struct servent *getservbyname(const char *, const char *); extern struct servent *getservbyport(int, const char *); extern struct servent *getservent(void); extern void setprotoent(int); extern void setservent(int); extern int *__h_errno_location(void); _________________________________________________________ 11.3.24. netinet/in.h extern int bindresvport(int, struct sockaddr_in *); _________________________________________________________ 11.3.25. netinet/ip.h /* * This header is architecture neutral * Please refer to the generic specification for details */ _________________________________________________________ 11.3.26. netinet/tcp.h /* * This header is architecture neutral * Please refer to the generic specification for details */ _________________________________________________________ 11.3.27. netinet/udp.h /* * This header is architecture neutral * Please refer to the generic specification for details */ _________________________________________________________ 11.3.28. nl_types.h extern int catclose(nl_catd); extern char *catgets(nl_catd, int, int, const char *); extern nl_catd catopen(const char *, int); _________________________________________________________ 11.3.29. poll.h extern int poll(struct pollfd *, nfds_t, int); _________________________________________________________ 11.3.30. pty.h extern int openpty(int *, int *, char *, struct termios *, struct winsize *); extern int forkpty(int *, char *, struct termios *, struct winsize *); _________________________________________________________ 11.3.31. pwd.h extern void endpwent(void); extern struct passwd *getpwent(void); extern struct passwd *getpwnam(char *); extern struct passwd *getpwuid(uid_t); extern void setpwent(void); extern int getpwnam_r(char *, struct passwd *, char *, size_t, struct passwd **); extern int getpwuid_r(uid_t, struct passwd *, char *, size_t, struct passwd **); _________________________________________________________ 11.3.32. regex.h extern int regcomp(regex_t *, const char *, int); extern size_t regerror(int, const regex_t *, char *, size_t); extern int regexec(const regex_t *, const char *, size_t, regmatch_t, int); extern void regfree(regex_t *); _________________________________________________________ 11.3.33. rpc/auth.h extern struct AUTH *authnone_create(void); extern int key_decryptsession(char *, union des_block *); extern bool_t xdr_opaque_auth(XDR *, struct opaque_auth *); _________________________________________________________ 11.3.34. rpc/clnt.h extern struct CLIENT *clnt_create(const char *, const u_long, const u_long, const char *); extern void clnt_pcreateerror(const char *); extern void clnt_perrno(enum clnt_stat); extern void clnt_perror(struct CLIENT *, const char *); extern char *clnt_spcreateerror(const char *); extern char *clnt_sperrno(enum clnt_stat); extern char *clnt_sperror(struct CLIENT *, const char *); _________________________________________________________ 11.3.35. rpc/pmap_clnt.h extern u_short pmap_getport(struct sockaddr_in *, const u_long, const u_long, u_int); extern bool_t pmap_set(const u_long, const u_long, int, u_short); extern bool_t pmap_unset(u_long, u_long); _________________________________________________________ 11.3.36. rpc/rpc_msg.h extern bool_t xdr_callhdr(XDR *, struct rpc_msg *); _________________________________________________________ 11.3.37. rpc/svc.h extern void svc_getreqset(fd_set *); extern bool_t svc_register(SVCXPRT *, rpcprog_t, rpcvers_t, __dispatch_fn_t, rpcprot_t); extern void svc_run(void); extern bool_t svc_sendreply(SVCXPRT *, xdrproc_t, caddr_t); extern void svcerr_auth(SVCXPRT *, enum auth_stat); extern void svcerr_decode(SVCXPRT *); extern void svcerr_noproc(SVCXPRT *); extern void svcerr_noprog(SVCXPRT *); extern void svcerr_progvers(SVCXPRT *, rpcvers_t, rpcvers_t); extern void svcerr_systemerr(SVCXPRT *); extern void svcerr_weakauth(SVCXPRT *); extern SVCXPRT *svctcp_create(int, u_int, u_int); extern SVCXPRT *svcudp_create(int); _________________________________________________________ 11.3.38. rpc/types.h /* * This header is architecture neutral * Please refer to the generic specification for details */ _________________________________________________________ 11.3.39. rpc/xdr.h extern bool_t xdr_array(XDR *, caddr_t *, u_int *, u_int, u_int, xdrproc_t); extern bool_t xdr_bool(XDR *, bool_t *); extern bool_t xdr_bytes(XDR *, char **, u_int *, u_int); extern bool_t xdr_char(XDR *, char *); extern bool_t xdr_double(XDR *, double *); extern bool_t xdr_enum(XDR *, enum_t *); extern bool_t xdr_float(XDR *, float *); extern void xdr_free(xdrproc_t, char *); extern bool_t xdr_int(XDR *, int *); extern bool_t xdr_long(XDR *, long int *); extern bool_t xdr_opaque(XDR *, caddr_t, u_int); extern bool_t xdr_pointer(XDR *, char **, u_int, xdrproc_t); extern bool_t xdr_reference(XDR *, caddr_t *, u_int, xdrproc_t); extern bool_t xdr_short(XDR *, short *); extern bool_t xdr_string(XDR *, char **, u_int); extern bool_t xdr_u_char(XDR *, u_char *); extern bool_t xdr_u_int(XDR *, u_int *); extern bool_t xdr_u_long(XDR *, u_long *); extern bool_t xdr_u_short(XDR *, u_short *); extern bool_t xdr_union(XDR *, enum_t *, char *, const struct xdr_discrim *, xdrproc_t); extern bool_t xdr_vector(XDR *, char *, u_int, u_int, xdrproc_t); extern bool_t xdr_void(void); extern bool_t xdr_wrapstring(XDR *, char **); extern void xdrmem_create(XDR *, caddr_t, u_int, enum xdr_op); extern void xdrrec_create(XDR *, u_int, u_int, caddr_t, int (*__readit) (char *p1, char *p2, int p3) , int (*__writeit) (char *p1, char *p2, int p3) ); extern typedef int bool_t xdrrec_eof(XDR *); _________________________________________________________ 11.3.40. sched.h extern int sched_get_priority_max(int); extern int sched_get_priority_min(int); extern int sched_getparam(pid_t, struct sched_param *); extern int sched_getscheduler(pid_t); extern int sched_rr_get_interval(pid_t, struct timespec *); extern int sched_setparam(pid_t, const struct sched_param *); extern int sched_setscheduler(pid_t, int, const struct sched_param *); extern int sched_yield(void); _________________________________________________________ 11.3.41. search.h extern int hcreate(size_t); extern ENTRY *hsearch(ENTRY, ACTION); extern void insque(void *, void *); extern void *lfind(const void *, const void *, size_t *, size_t, __compar_fn_t); extern void *lsearch(const void *, void *, size_t *, size_t, __compar_fn_t); extern void remque(void *); extern void hdestroy(void); extern void *tdelete(const void *, void **, __compar_fn_t); extern void *tfind(const void *, void *const *, __compar_fn_t); extern void *tsearch(const void *, void **, __compar_fn_t); extern void twalk(const void *, __action_fn_t); _________________________________________________________ 11.3.42. setjmp.h typedef long int __jmp_buf[70] __attribute__ ((aligned(16))); extern int __sigsetjmp(jmp_buf, int); extern void longjmp(jmp_buf, int); extern void siglongjmp(sigjmp_buf, int); extern void _longjmp(jmp_buf, int); extern int _setjmp(jmp_buf); _________________________________________________________ 11.3.43. signal.h #define SIGEV_PAD_SIZE ((SIGEV_MAX_SIZE/sizeof(int))-4) #define SI_PAD_SIZE ((SI_MAX_SIZE/sizeof(int))-4) struct sigaction { union { sighandler_t _sa_handler; void (*_sa_sigaction) (int, siginfo_t *, void *); } __sigaction_handler; unsigned long int sa_flags; sigset_t sa_mask; }; #define MINSIGSTKSZ 131027 #define SIGSTKSZ 262144 struct ia64_fpreg { union { unsigned long int bits[2]; long double __dummy; } u; }; struct sigcontext { unsigned long int sc_flags; unsigned long int sc_nat; stack_t sc_stack; unsigned long int sc_ip; unsigned long int sc_cfm; unsigned long int sc_um; unsigned long int sc_ar_rsc; unsigned long int sc_ar_bsp; unsigned long int sc_ar_rnat; unsigned long int sc_ar_ccv; unsigned long int sc_ar_unat; unsigned long int sc_ar_fpsr; unsigned long int sc_ar_pfs; unsigned long int sc_ar_lc; unsigned long int sc_pr; unsigned long int sc_br[8]; unsigned long int sc_gr[32]; struct ia64_fpreg sc_fr[128]; unsigned long int sc_rbs_base; unsigned long int sc_loadrs; unsigned long int sc_ar25; unsigned long int sc_ar26; unsigned long int sc_rsvd[12]; unsigned long int sc_mask; }; extern int __libc_current_sigrtmax(void); extern int __libc_current_sigrtmin(void); extern sighandler_t __sysv_signal(int, sighandler_t); extern char *const _sys_siglist(void); extern int killpg(pid_t, int); extern void psignal(int, const char *); extern int raise(int); extern int sigaddset(sigset_t *, int); extern int sigandset(sigset_t *, const sigset_t *, const sigset_t *); extern int sigdelset(sigset_t *, int); extern int sigemptyset(sigset_t *); extern int sigfillset(sigset_t *); extern int sighold(int); extern int sigignore(int); extern int siginterrupt(int, int); extern int sigisemptyset(const sigset_t *); extern int sigismember(const sigset_t *, int); extern int sigorset(sigset_t *, const sigset_t *, const sigset_t *); extern int sigpending(sigset_t *); extern int sigrelse(int); extern sighandler_t sigset(int, sighandler_t); extern int pthread_kill(pthread_t, int); extern int pthread_sigmask(int, sigset_t *, sigset_t *); extern int sigaction(int, const struct sigaction *, struct sigaction *); extern int sigwait(sigset_t *, int *); extern int kill(pid_t, int); extern int sigaltstack(const struct sigaltstack *, struct sigaltstack *); extern sighandler_t signal(int, sighandler_t); extern int sigpause(int); extern int sigprocmask(int, const sigset_t *, sigset_t *); extern int sigreturn(struct sigcontext *); extern int sigsuspend(const sigset_t *); extern int sigqueue(pid_t, int, const union sigval); extern int sigwaitinfo(const sigset_t *, siginfo_t *); extern int sigtimedwait(const sigset_t *, siginfo_t *, const struct timespec *); extern sighandler_t bsd_signal(int, sighandler_t); _________________________________________________________ 11.3.44. stddef.h typedef long int ptrdiff_t; typedef unsigned long int size_t; _________________________________________________________ 11.3.45. stdio.h #define __IO_FILE_SIZE 216 extern char *const _sys_errlist(void); extern void clearerr(FILE *); extern int fclose(FILE *); extern FILE *fdopen(int, const char *); extern int fflush_unlocked(FILE *); extern int fileno(FILE *); extern FILE *fopen(const char *, const char *); extern int fprintf(FILE *, const char *, ...); extern int fputc(int, FILE *); extern FILE *freopen(const char *, const char *, FILE *); extern FILE *freopen64(const char *, const char *, FILE *); extern int fscanf(FILE *, const char *, ...); extern int fseek(FILE *, long int, int); extern int fseeko(FILE *, off_t, int); extern int fseeko64(FILE *, loff_t, int); extern off_t ftello(FILE *); extern loff_t ftello64(FILE *); extern int getchar(void); extern int getchar_unlocked(void); extern int getw(FILE *); extern int pclose(FILE *); extern void perror(const char *); extern FILE *popen(const char *, const char *); extern int printf(const char *, ...); extern int putc_unlocked(int, FILE *); extern int putchar(int); extern int putchar_unlocked(int); extern int putw(int, FILE *); extern int remove(const char *); extern void rewind(FILE *); extern int scanf(const char *, ...); extern void setbuf(FILE *, char *); extern int sprintf(char *, const char *, ...); extern int sscanf(const char *, const char *, ...); extern FILE *stderr(void); extern FILE *stdin(void); extern FILE *stdout(void); extern char *tempnam(const char *, const char *); extern FILE *tmpfile64(void); extern FILE *tmpfile(void); extern char *tmpnam(char *); extern int vfprintf(FILE *, const char *, va_list); extern int vprintf(const char *, va_list); extern int feof(FILE *); extern int ferror(FILE *); extern int fflush(FILE *); extern int fgetc(FILE *); extern int fgetpos(FILE *, fpos_t *); extern char *fgets(char *, int, FILE *); extern int fputs(const char *, FILE *); extern size_t fread(void *, size_t, size_t, FILE *); extern int fsetpos(FILE *, const fpos_t *); extern long int ftell(FILE *); extern size_t fwrite(const void *, size_t, size_t, FILE *); extern int getc(FILE *); extern int putc(int, FILE *); extern int puts(const char *); extern int setvbuf(FILE *, char *, int, size_t); extern int snprintf(char *, size_t, const char *, ...); extern int ungetc(int, FILE *); extern int vsnprintf(char *, size_t, const char *, va_list); extern int vsprintf(char *, const char *, va_list); extern void flockfile(FILE *); extern int asprintf(char **, const char *, ...); extern int fgetpos64(FILE *, fpos64_t *); extern FILE *fopen64(const char *, const char *); extern int fsetpos64(FILE *, const fpos64_t *); extern int ftrylockfile(FILE *); extern void funlockfile(FILE *); extern int getc_unlocked(FILE *); extern void setbuffer(FILE *, char *, size_t); extern int vasprintf(char **, const char *, va_list); extern int vdprintf(int, const char *, va_list); extern int vfscanf(FILE *, const char *, va_list); extern int vscanf(const char *, va_list); extern int vsscanf(const char *, const char *, va_list); extern size_t __fpending(FILE *); _________________________________________________________ 11.3.46. stdlib.h extern double __strtod_internal(const char *, char **, int); extern float __strtof_internal(const char *, char **, int); extern long int __strtol_internal(const char *, char **, int, int); extern long double __strtold_internal(const char *, char **, int); extern long long int __strtoll_internal(const char *, char **, int, int); extern unsigned long int __strtoul_internal(const char *, char **, int, int); extern unsigned long long int __strtoull_internal(const char *, char **, int, int); extern long int a64l(const char *); extern void abort(void); extern int abs(int); extern double atof(const char *); extern int atoi(char *); extern long int atol(char *); extern long long int atoll(const char *); extern void *bsearch(const void *, const void *, size_t, size_t, __compar_fn_t); extern div_t div(int, int); extern double drand48(void); extern char *ecvt(double, int, int *, int *); extern double erand48(unsigned short); extern void exit(int); extern char *fcvt(double, int, int *, int *); extern char *gcvt(double, int, char *); extern char *getenv(const char *); extern int getsubopt(char **, char *const *, char **); extern int grantpt(int); extern long int jrand48(unsigned short); extern char *l64a(long int); extern long int labs(long int); extern void lcong48(unsigned short); extern ldiv_t ldiv(long int, long int); extern long long int llabs(long long int); extern lldiv_t lldiv(long long int, long long int); extern long int lrand48(void); extern int mblen(const char *, size_t); extern size_t mbstowcs(wchar_t *, const char *, size_t); extern int mbtowc(wchar_t *, const char *, size_t); extern char *mktemp(char *); extern long int mrand48(void); extern long in