1.1. General

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

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

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

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

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

1.2. Module Specific Scope

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

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

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.

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.

3.1. Relevant Libraries

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

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

3.2. LSB Implementation Conformance

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

A conforming implementation shall satisfy the following requirements:

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

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

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

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

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

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

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

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

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

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

3.3. LSB Application Conformance

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

A conforming application shall satisfy the following requirements:

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

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

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

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

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

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

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

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

8.1. Machine Interface

8.2. Function Calling Sequence

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

8.3. Operating System Interface

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

8.4. Process Initialization

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

8.5. Coding Examples

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

8.6. C Stack Frame

8.7. Debug Information

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

9.1. Introduction

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

9.2. ELF Header

9.3. Sections

9.4. Symbol Table

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

9.5. Relocation

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

10.1. Introduction

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

10.2. Program Header

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

10.3. Program Loading

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

10.4. Dynamic Linking

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

11.1. Program Interpreter/Dynamic Linker

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

11.2. Interfaces for libc

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

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

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.

enum {
    _ISupper = 1,
    _ISlower = 2,
    _ISalpha = 4,
    _ISdigit = 8,
    _ISxdigit = 16,
    _ISspace = 32,
    _ISprint = 64,
    _ISgraph = 128,
    _ISblank = 256,
    _IScntrl = 512,
    _ISpunct = 1024,
    _ISalnum = 2048
};

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

#define EDEADLOCK	58

#define O_LARGEFILE	0200000

#define F_GETLK64	12
#define F_SETLK64	13
#define F_SETLKW64	14

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

#define ULONG_MAX	0xFFFFFFFFUL
#define LONG_MAX	2147483647L

#define CHAR_MIN	0
#define CHAR_MAX	255

#define PTHREAD_STACK_MIN	16384

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

typedef long int __jmp_buf[112] __attribute__ ((aligned(16)));

struct pt_regs {
    unsigned long int gpr[32];
    unsigned long int nip;
    unsigned long int msr;
    unsigned long int orig_gpr3;
    unsigned long int ctr;
    unsigned long int link;
    unsigned long int xer;
    unsigned long int ccr;
    unsigned long int mq;
    unsigned long int trap;
    unsigned long int dar;
    unsigned long int dsisr;
    unsigned long int result;
};

#define SIGEV_PAD_SIZE	((SIGEV_MAX_SIZE/sizeof(int))-3)

#define SI_PAD_SIZE	((SI_MAX_SIZE/sizeof(int))-3)

struct sigaction {
    union {
	sighandler_t _sa_handler;
	void (*_sa_sigaction) (int, siginfo_t *, void *);
    } __sigaction_handler;
    sigset_t sa_mask;
    unsigned long int sa_flags;
    void (*sa_restorer) (void);
};

#define MINSIGSTKSZ	2048
#define SIGSTKSZ	8192

struct sigcontext {
    long int _unused[4];
    int signal;
    unsigned long int handler;
    unsigned long int oldmask;
    struct pt_regs *regs;
};

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

typedef long int wchar_t;
typedef unsigned int size_t;
typedef int ptrdiff_t;

#define INT64_C(c)	c ## LL
#define INTMAX_C(c)	c ## LL
#define __INT64_C(c)	c ## LL
#define UINT64_C(c)	c ## ULL
#define UINTMAX_C(c)	c ## ULL
#define __UINT64_C(c)	c ## ULL

#define INTPTR_MIN	(-2147483647-1)
#define INT_FAST16_MIN	(-2147483647-1)
#define INT_FAST32_MIN	(-2147483647-1)
#define PTRDIFF_MIN	(-2147483647-1)
#define INTPTR_MAX	(2147483647)
#define INT_FAST16_MAX	(2147483647)
#define INT_FAST32_MAX	(2147483647)
#define PTRDIFF_MAX	(2147483647)
#define SIZE_MAX	(4294967295U)
#define UINTPTR_MAX	(4294967295U)
#define UINT_FAST16_MAX	(4294967295U)
#define UINT_FAST32_MAX	(4294967295U)

typedef long long int int64_t;
typedef long long int intmax_t;
typedef unsigned long long int uintmax_t;
typedef int intptr_t;
typedef unsigned int uintptr_t;
typedef unsigned long long int uint64_t;
typedef long long int int_least64_t;
typedef unsigned long long int uint_least64_t;
typedef int int_fast16_t;
typedef int int_fast32_t;
typedef long long int int_fast64_t;
typedef unsigned int uint_fast16_t;
typedef unsigned int uint_fast32_t;
typedef unsigned long long int uint_fast64_t;

#define __IO_FILE_SIZE	152

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

#define TIOCGWINSZ	0x40087468
#define TIOCNOTTY	0x5422
#define FIONREAD	1074030207

struct ipc_perm {
    key_t __key;
    uid_t uid;
    gid_t gid;
    uid_t cuid;
    uid_t cgid;
    mode_t mode;
    long int __seq;
    int __pad1;
    unsigned long long int __unused1;
    unsigned long long int __unused2;
};

#define MCL_FUTURE	16384
#define MCL_CURRENT	8192

typedef unsigned long int msgqnum_t;
typedef unsigned long int msglen_t;

struct msqid_ds {
    struct ipc_perm msg_perm;
    unsigned int __unused1;
    time_t msg_stime;
    unsigned int __unused2;
    time_t msg_rtime;
    unsigned int __unused3;
    time_t msg_ctime;
    unsigned long int __msg_cbytes;
    msgqnum_t msg_qnum;
    msglen_t msg_qbytes;
    pid_t msg_lspid;
    pid_t msg_lrpid;
    unsigned long int __unused4;
    unsigned long int __unused5;
};

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

struct semid_ds {
    struct ipc_perm sem_perm;
    unsigned int __unused1;
    time_t sem_otime;
    unsigned int __unused2;
    time_t sem_ctime;
    unsigned long int sem_nsems;
    unsigned long int __unused3;
    unsigned long int __unused4;
};

#define SHMLBA	(__getpagesize())

typedef unsigned long int shmatt_t;

struct shmid_ds {
    struct ipc_perm shm_perm;
    unsigned int __unused1;
    time_t shm_atime;
    unsigned int __unused2;
    time_t shm_dtime;
    unsigned int __unused3;
    time_t shm_ctime;
    unsigned int __unused4;
    size_t shm_segsz;
    pid_t shm_cpid;
    pid_t shm_lpid;
    shmatt_t shm_nattch;
    unsigned long int __unused5;
    unsigned long int __unused6;
};

typedef uint32_t __ss_aligntype;

#define SO_RCVLOWAT	16
#define SO_SNDLOWAT	17
#define SO_RCVTIMEO	18
#define SO_SNDTIMEO	19

#define _STAT_VER	3

struct stat {
    dev_t st_dev;
    unsigned short __pad1;
    ino_t st_ino;
    mode_t st_mode;
    nlink_t st_nlink;
    uid_t st_uid;
    gid_t st_gid;
    dev_t st_rdev;
    unsigned short __pad2;
    off_t st_size;
    blksize_t st_blksize;
    blkcnt_t st_blocks;
    struct timespec st_atim;
    struct timespec st_mtim;
    struct timespec st_ctim;
    unsigned long int __unused4;
    unsigned long int __unused5;
};
struct stat64 {
    dev_t st_dev;
    ino64_t st_ino;
    mode_t st_mode;
    nlink_t st_nlink;
    uid_t st_uid;
    gid_t st_gid;
    dev_t st_rdev;
    unsigned short __pad2;
    off64_t st_size;
    blksize_t st_blksize;
    blkcnt64_t st_blocks;
    struct timespec st_atim;
    struct timespec st_mtim;
    struct timespec st_ctim;
    unsigned long int __unused4;
    unsigned long int __unused5;
};

struct statfs {
    int f_type;
    int f_bsize;
    fsblkcnt_t f_blocks;
    fsblkcnt_t f_bfree;
    fsblkcnt_t f_bavail;
    fsfilcnt_t f_files;
    fsfilcnt_t f_ffree;
    fsid_t f_fsid;
    int f_namelen;
    int f_frsize;
    int f_spare[5];
};
struct statfs64 {
    int f_type;
    int f_bsize;
    fsblkcnt64_t f_blocks;
    fsblkcnt64_t f_bfree;
    fsblkcnt64_t f_bavail;
    fsfilcnt64_t f_files;
    fsfilcnt64_t f_ffree;
    fsid_t f_fsid;
    int f_namelen;
    int f_frsize;
    int f_spare[5];
};

struct statvfs {
    unsigned long int f_bsize;
    unsigned long int f_frsize;
    fsblkcnt_t f_blocks;
    fsblkcnt_t f_bfree;
    fsblkcnt_t f_bavail;
    fsfilcnt_t f_files;
    fsfilcnt_t f_ffree;
    fsfilcnt_t f_favail;
    unsigned long int f_fsid;
    int __f_unused;
    unsigned long int f_flag;
    unsigned long int f_namemax;
    int __f_spare[6];
};
struct statvfs64 {
    unsigned long int f_bsize;
    unsigned long int f_frsize;
    fsblkcnt64_t f_blocks;
    fsblkcnt64_t f_bfree;
    fsblkcnt64_t f_bavail;
    fsfilcnt64_t f_files;
    fsfilcnt64_t f_ffree;
    fsfilcnt64_t f_favail;
    unsigned long int f_fsid;
    int __f_unused;
    unsigned long int f_flag;
    unsigned long int f_namemax;
    int __f_spare[6];
};

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

typedef int32_t ssize_t;

#define __FDSET_LONGS	32

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

#define TAB1	1024
#define CR3	12288
#define CRDLY	12288
#define FF1	16384
#define FFDLY	16384
#define XCASE	16384
#define ONLCR	2
#define TAB2	2048
#define TAB3	3072
#define TABDLY	3072
#define BS1	32768
#define BSDLY	32768
#define OLCUC	4
#define CR1	4096
#define IUCLC	4096
#define VT1	65536
#define VTDLY	65536
#define NLDLY	768
#define CR2	8192

#define VWERASE	10
#define VREPRINT	11
#define VSUSP	12
#define VSTART	13
#define VSTOP	14
#define VDISCARD	16
#define VMIN	5
#define VEOL	6
#define VEOL2	8
#define VSWTC	9

#define IXOFF	1024
#define IXON	512

#define CSTOPB	1024
#define HUPCL	16384
#define CREAD	2048
#define CS6	256
#define CLOCAL	32768
#define PARENB	4096
#define CS7	512
#define VTIME	7
#define CS8	768
#define CSIZE	768
#define PARODD	8192

#define NOFLSH	0x80000000
#define ECHOKE	1
#define IEXTEN	1024
#define ISIG	128
#define ECHONL	16
#define ECHOE	2
#define ICANON	256
#define ECHOPRT	32
#define ECHOK	4
#define TOSTOP	4194304
#define PENDIN	536870912
#define ECHOCTL	64
#define FLUSHO	8388608

typedef struct _libc_vrstate {
    unsigned int vrregs[128];
    unsigned int vrsave;
    unsigned int _pad[2];
    unsigned int vscr;
} vrregset_t __attribute__ ((__aligned__(16)));

#define NGREG	48

typedef unsigned long int gregset_t[48];

typedef struct _libc_fpstate {
    double fpregs[32];
    double fpscr;
    int _pad[2];
} fpregset_t;

typedef struct {
    gregset_t gregs;
    fpregset_t fpregs;
    vrregset_t vrregs;
} mcontext_t;

union uc_regs_ptr {
    struct pt_regs *regs;
    mcontext_t *uc_regs;
};

typedef struct ucontext {
    unsigned long int uc_flags;
    struct ucontext *uc_link;
    stack_t uc_stack;
    int uc_pad[7];
    union uc_regs_ptr uc_mcontext;
    sigset_t uc_sigmask;
    char uc_reg_space[sizeof(mcontext_t) + 12];
} ucontext_t;

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

struct lastlog {
    time_t ll_time;
    char ll_line[UT_LINESIZE];
    char ll_host[UT_HOSTSIZE];
};

struct utmp {
    short ut_type;
    pid_t ut_pid;
    char ut_line[UT_LINESIZE];
    char ut_id[4];
    char ut_user[UT_NAMESIZE];
    char ut_host[UT_HOSTSIZE];
    struct exit_status ut_exit;
    long int ut_session;
    struct timeval ut_tv;
    int32_t ut_addr_v6[4];
    char __unused[20];
};

struct utmpx {
    short ut_type;
    pid_t ut_pid;
    char ut_line[UT_LINESIZE];
    char ut_id[4];
    char ut_user[UT_NAMESIZE];
    char ut_host[UT_HOSTSIZE];
    struct exit_status ut_exit;
    long int ut_session;
    struct timeval ut_tv;
    int32_t ut_addr_v6[4];
    char __unused[20];
};

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

11.4. Interfaces for libm

Table 11-33 defines the library name and shared object name for the libm library

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

11.5. Data Definitions for libm

This section defines global identifiers and their values that are associated with interfaces contained in libm. 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.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

#define FE_INVALID	(1 << (31 - 2))
#define FE_OVERFLOW	(1 << (31 - 3))
#define FE_UNDERFLOW	(1 << (31 - 4))
#define FE_DIVBYZERO	(1 << (31 - 5))
#define FE_INEXACT	(1 << (31 - 6))

#define FE_ALL_EXCEPT	\
	(FE_INEXACT | FE_DIVBYZERO | FE_UNDERFLOW | FE_OVERFLOW | FE_INVALID)

#define FE_TONEAREST	0
#define FE_TOWARDZERO	1
#define FE_UPWARD	2
#define FE_DOWNWARD	3

typedef unsigned int fexcept_t;

typedef double fenv_t;

#define FE_DFL_ENV	(&__fe_dfl_env)

#define fpclassify(x)	\
	(sizeof (x) == sizeof (float) ? __fpclassifyf (x) : __fpclassify (x) )
#define signbit(x)	\
	(sizeof (x) == sizeof (float)? __signbitf (x): __signbit (x))
#define isfinite(x)	\
     (sizeof (x) == sizeof (float) ? __finitef (x) : __finite (x))
#define isinf(x)	\
     (sizeof (x) == sizeof (float) ? __isinff (x) : __isinf (x))
#define isnan(x)	\
     (sizeof (x) == sizeof (float) ? __isnanf (x) : __isnan (x))

#define HUGE_VALL	0x1.0p2047L

#define FP_ILOGB0	-2147483647
#define FP_ILOGBNAN	2147483647

11.6. Interfaces for libpthread

Table 11-37 defines the library name and shared object name for the libpthread library

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

11.7. Data Definitions for libpthread

This section defines global identifiers and their values that are associated with interfaces contained in libpthread. 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.

#define __SIZEOF_PTHREAD_BARRIER_T	20

typedef union {
    char __size[__SIZEOF_PTHREAD_BARRIER_T];
    long int __align;
} pthread_barrier_t;

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

11.8. Interfaces for libgcc_s

Table 11-43 defines the library name and shared object name for the libgcc_s library

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

11.9. Data Definitions for libgcc_s

This section defines global identifiers and their values that are associated with interfaces contained in libgcc_s. 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.

typedef _Unwind_Reason_Code(*_Unwind_Stop_Fn) (int version,
					       _Unwind_Action actions,
					       _Unwind_Exception_Class
					       exceptionClass,
					       struct _Unwind_Exception *
					       exceptionObject,
					       struct _Unwind_Context *
					       context,
					       void *stop_parameter);

typedef _Unwind_Reason_Code(*_Unwind_Trace_Fn) (struct _Unwind_Context *,
						void *);
extern void _Unwind_DeleteException(struct _Unwind_Exception *);
extern fde *_Unwind_Find_FDE(void *, struct dwarf_eh_base *);
extern _Unwind_Ptr _Unwind_GetDataRelBase(struct _Unwind_Context *);
extern _Unwind_Word _Unwind_GetGR(struct _Unwind_Context *, int);
extern _Unwind_Ptr _Unwind_GetIP(struct _Unwind_Context *);
extern _Unwind_Ptr _Unwind_GetLanguageSpecificData(struct _Unwind_Context
						   *, unsigned int);
extern _Unwind_Ptr _Unwind_GetRegionStart(struct _Unwind_Context *);
extern _Unwind_Reason_Code _Unwind_RaiseException(struct _Unwind_Exception
						  *);
extern void _Unwind_SetIP(struct _Unwind_Context *, unsigned int);
extern void _Unwind_Resume(struct _Unwind_Exception *);
extern void _Unwind_SetGR(struct _Unwind_Context *, int, u_int64_t);
extern _Unwind_Ptr _Unwind_GetTextRelBase(struct _Unwind_Context *);
extern _Unwind_Ptr _Unwind_ForcedUnwind(struct _Unwind_Exception *,
					_Unwind_Stop_Fn, void *);
extern _Unwind_Reason_Code _Unwind_Backtrace(_Unwind_Trace_Fn, void *);
extern _Unwind_Reason_Code _Unwind_GetCFA(struct _Unwind_Context *);
extern _Unwind_Reason_Code _Unwind_Resume_or_Rethrow(struct
						     _Unwind_Exception *);
extern void *_Unwind_FindEnclosingFunction(void *);

11.10. Interface Definitions for libgcc_s

The interfaces defined on the following pages are included in libgcc_s and are defined by this specification. Unless otherwise noted, these interfaces shall be included in the source standard.

Other interfaces listed in Section 11.8 shall behave as described in the referenced base document. For interfaces referencing LSB and not listed below, please see the generic part of the specification.

_Unwind_DeleteException

_Unwind_Find_FDE

_Unwind_ForcedUnwind

_Unwind_GetDataRelBase

_Unwind_GetGR

_Unwind_GetIP

_Unwind_GetLanguageSpecificData

_Unwind_GetRegionStart

_Unwind_GetTextRelBase

_Unwind_RaiseException

_Unwind_Resume

_Unwind_SetGR

_Unwind_SetIP

11.11. Interfaces for libdl

Table 11-45 defines the library name and shared object name for the libdl library

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

11.12. Data Definitions for libdl

This section defines global identifiers and their values that are associated with interfaces contained in libdl. 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.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

11.13. Interfaces for libcrypt

Table 11-47 defines the library name and shared object name for the libcrypt library

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

12.1. Interfaces for libz

Table 12-1 defines the library name and shared object name for the libz library

12.2. Data Definitions for libz

This section defines global identifiers and their values that are associated with interfaces contained in libz. 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.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

12.3. Interfaces for libncurses

Table 12-2 defines the library name and shared object name for the libncurses library

12.4. Data Definitions for libncurses

This section defines global identifiers and their values that are associated with interfaces contained in libncurses. 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.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

12.5. Interfaces for libutil

Table 12-3 defines the library name and shared object name for the libutil library

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

13.1. Package Dependencies

The LSB runtime environment shall provde the following dependencies.

This dependency shall have a version of 3.0.

Other LSB modules may add additional dependencies; such dependencies shall have the format lsb-module-ppc32.

13.2. Package Architecture Considerations

All packages must specify an architecture of ppc. A LSB runtime environment must accept an architecture of ppc even if the native architecture is different.

The archnum value in the Lead Section shall be 0x0005.