General

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

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

The LSB-generic document shall be used in conjunction with an architecture-specific supplement. Whenever a section of the LSB-generic specification shall be supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture supplement. Architecture supplements may also contain additional information that is not referenced in the LSB-generic document.

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

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

Module Specific Scope

This is the PPC64 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.

Relevant Libraries

The libraries listed in Table 3-1 shall be available on PPC64 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.

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

LSB Implementation Conformance

An implementation shall satisfy the following requirements:

• The implementation shall implement fully the architecture described in the hardware manual for the target processor architecture.

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

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

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

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

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

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

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

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

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

LSB Application Conformance

An application shall satisfy the following requirements:

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

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

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

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

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

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

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

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

Processor Architecture

The PowerPC Architecture is specified by the following documents:

• 64-bit PowerPC ELF ABI Supplement, Version 1.7

• The PowerPC ™ Architecture: A Specification for a new family of RISC processors

• The PowerPC Architecture Book I changes

• The PowerPC Architecture Book II changes

• The PowerPC Architecture Book III changes

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

Only instructions which do not require elevated privileges may be used.

Applications may not make system calls directly. The interfaces in the C library must be used instead.

An implementation must support the 64-bit computation mode as described in The PowerPC ™ Architecture: A Specification for a new family of RISC processors.

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

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

Data Representation

LSB-conforming applications shall use the data representation as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement, Version 1.7.

Byte Ordering

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

Fundamental Types

LSB-conforming applications shall use the fundamental types as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement, Version 1.7.

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

Aggregates and Unions

Bit Fields

Registers

Stack Frame

Parameter Passing

Return Values

Function Descriptors

Mandatory Fields

Optional Fields

Registers

Process Stack

Code Model Overview

The TOC Section

TOC Assembly Language Syntax

Function Prologue and Epilogue

Register Saving and Restoring Functions

Saving General Registers Only

Saving General Registers and Floating Point Registers

Saving Floating Point Registers Only

Save and Restore Services

Data Objects

Function Calls

Branching

Dynamic Stack Space Allocation

Symbol Values

Relocation Types

Dynamic Section

The following dynamic entries are defined in the 64-bit PowerPC ELF ABI Supplement, Version 1.7, Chapter 5.2.

In addtion the following dynamic entries are also supported:

Global Offset Table

See 64-bit PowerPC ELF ABI Supplement, Version 1.7, Chapter 5.2.

Function Addresses

Procedure Linkage Table

Program Interpreter/Dynamic Linker

The LSB specifies the Program Interpreter to be /lib64/ld-lsb-ppc64.so.2.

Interfaces for libc

Table 1-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:

---

Socket Interface

---

Interfaces for Socket Interface

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

Table 1-10. libc - Socket Interface Function Interfaces

__h_errno_location(GLIBC_2.3) [1]	gethostid(GLIBC_2.3) [2]	listen(GLIBC_2.3) [2]	sendmsg(GLIBC_2.3) [2]	socketpair(GLIBC_2.3) [2]
accept(GLIBC_2.3) [2]	gethostname(GLIBC_2.3) [2]	recv(GLIBC_2.3) [2]	sendto(GLIBC_2.3) [2]
bind(GLIBC_2.3) [2]	getpeername(GLIBC_2.3) [2]	recvfrom(GLIBC_2.3) [2]	setsockopt(GLIBC_2.3) [1]
bindresvport(GLIBC_2.3) [1]	getsockname(GLIBC_2.3) [2]	recvmsg(GLIBC_2.3) [2]	shutdown(GLIBC_2.3) [2]
connect(GLIBC_2.3) [2]	getsockopt(GLIBC_2.3) [2]	send(GLIBC_2.3) [2]	socket(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. Linux Standard Base

[2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX® Specification(SUS) V3

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

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

Table 1-11. libc - Socket Interface Deprecated Function Interfaces

gethostbyname_r(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. Linux Standard Base

---

Regular Expressions

---

Interfaces for Regular Expressions

An LSB conforming implementation shall provide the architecture specific functions for Regular Expressions specified in Table 1-15, with the full functionality as described in the referenced underlying specification.

Table 1-15. libc - Regular Expressions Function Interfaces

regcomp(GLIBC_2.3) [1]

regerror(GLIBC_2.3) [1]

regexec(GLIBC_2.3) [1]

regfree(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX® Specification(SUS) V3

An LSB conforming implementation shall provide the architecture specific deprecated functions for Regular Expressions specified in Table 1-16, with the full functionality as described in the referenced underlying specification.

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

Table 1-16. libc - Regular Expressions Deprecated Function Interfaces

advance(GLIBC_2.3) [1]

re_comp(GLIBC_2.3) [1]

re_exec(GLIBC_2.3) [1]

step(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606)

An LSB conforming implementation shall provide the architecture specific deprecated data interfaces for Regular Expressions specified in Table 1-17, with the full functionality as described in the referenced underlying specification.

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

Table 1-17. libc - Regular Expressions Deprecated Data Interfaces

loc1(GLIBC_2.3) [1]

loc2(GLIBC_2.3) [1]

locs(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606)

---

Time Manipulation

---

Interfaces for Time Manipulation

An LSB conforming implementation shall provide the architecture specific functions for Time Manipulation specified in Table 1-19, with the full functionality as described in the referenced underlying specification.

Table 1-19. libc - Time Manipulation Function Interfaces

adjtime(GLIBC_2.3) [1]	ctime(GLIBC_2.3) [2]	gmtime(GLIBC_2.3) [2]	localtime_r(GLIBC_2.3) [2]	ualarm(GLIBC_2.3) [2]
asctime(GLIBC_2.3) [2]	ctime_r(GLIBC_2.3) [2]	gmtime_r(GLIBC_2.3) [2]	mktime(GLIBC_2.3) [2]
asctime_r(GLIBC_2.3) [2]	difftime(GLIBC_2.3) [2]	localtime(GLIBC_2.3) [2]	tzset(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. Linux Standard Base

[2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX® Specification(SUS) V3

An LSB conforming implementation shall provide the architecture specific deprecated functions for Time Manipulation specified in Table 1-20, with the full functionality as described in the referenced underlying specification.

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

Table 1-20. libc - Time Manipulation Deprecated Function Interfaces

adjtimex(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. Linux Standard Base

An LSB conforming implementation shall provide the architecture specific data interfaces for Time Manipulation specified in Table 1-21, with the full functionality as described in the referenced underlying specification.

Table 1-21. libc - Time Manipulation Data Interfaces

__daylight(GLIBC_2.3) [1]	__tzname(GLIBC_2.3) [1]	timezone(GLIBC_2.3) [2]
__timezone(GLIBC_2.3) [1]	daylight(GLIBC_2.3) [2]	tzname(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. Linux Standard Base

[2]. ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX® Specification(SUS) V3

Data Definitions for libc

This section defines global identifiers and their values that are associated with interfaces contained in libc. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content.

These definitions are intended to supplement those provided in the referenced underlying specifications.

This specification uses ISO/IEC 9899 C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

#define EDEADLOCK	58

typedef long intmax_t;
typedef unsigned long uintmax_t;
typedef unsigned long uintptr_t;
typedef unsigned long uint64_t;

#define ULONG_MAX	0xFFFFFFFFFFFFFFFFUL
#define LONG_MAX	9223372036854775807L

#define CHAR_MIN	0
#define CHAR_MAX	255

typedef long __jmp_buf[40];

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

struct sigaction
{
  union
  {
    sighandler_t _sa_handler;
    void (*_sa_sigaction) (int, siginfo_t *, void *);
  }
  __sigaction_handler;
  sigset_t sa_mask;
  int sa_flags;
  void (*sa_restorer) (void);
}
 ;
#define MINSIGSTKSZ	2048
#define SIGSTKSZ	8192

struct sigcontext
{
  unsigned long _unused[4];
  int signal;
  unsigned long handler;
  unsigned long oldmask;
  struct pt_regs *regs;
  unsigned long gp_regs[48];
  double fp_regs[33];
}
 ;

typedef unsigned long size_t;
typedef long ptrdiff_t;

#define FIONREAD	1074030207
#define TIOCNOTTY	21538

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

#define MCL_FUTURE	16384
#define MCL_CURRENT	8192

typedef unsigned long msglen_t;
typedef unsigned long msgqnum_t;

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

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

#define SHMLBA	(__getpagesize())

typedef unsigned long shmatt_t;

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

typedef uint64_t __ss_aligntype;

#define _STAT_VER	1

struct stat
{
  dev_t st_dev;
  ino_t st_ino;
  nlink_t st_nlink;
  mode_t st_mode;
  uid_t st_uid;
  gid_t st_gid;
  int __pad2;
  dev_t st_rdev;
  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 __unused4;
  unsigned long __unused5;
  unsigned long __unused6;
}
 ;
struct stat64
{
  dev_t st_dev;
  ino64_t st_ino;
  nlink_t st_nlink;
  mode_t st_mode;
  uid_t st_uid;
  gid_t st_gid;
  int __pad2;
  dev_t st_rdev;
  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 __unused4;
  unsigned long __unused5;
  unsigned long __unused6;
}
 ;

struct statvfs
{
  unsigned long f_bsize;
  unsigned long 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 f_fsid;
  unsigned long f_flag;
  unsigned long f_namemax;
  int __f_spare[6];
}
 ;
struct statvfs64
{
  unsigned long f_bsize;
  unsigned long f_frsize;
  fsblkcnt64_t f_blocks;
  fsblkcnt64_t f_bfree;
  fsblkcnt64_t f_bavail;
  fsfilcnt64_t f_files;
  fsfilcnt64_t f_ffree;
  fsfilcnt64_t f_favail;
  unsigned long f_fsid;
  unsigned long f_flag;
  unsigned long f_namemax;
  int __f_spare[6];
}
 ;

typedef long int64_t;

typedef int64_t ssize_t;

#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

#define NGREG	48

typedef struct sigcontext mcontext_t;

typedef struct ucontext
{
  unsigned long uc_flags;
  struct ucontext *uc_link;
  stack_t uc_stack;
  sigset_t uc_sigmask;
  mcontext_t uc_mcontext;
}
ucontext_t;

typedef long intptr_t;

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

struct utmp
{
  short ut_type;
  pid_t ut_pid;
  char ut_line[UT_LINESIZE];
  char ut_id[4];
  char ut_user[UT_NAMESIZE];
  char ut_host[UT_HOSTSIZE];
  struct exit_status ut_exit;
  int32_t ut_session;
  struct
  {
    int32_t tv_sec;
    int32_t tv_usec;
  }
  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;
  int32_t ut_session;
  struct
  {
    int32_t tv_sec;
    int32_t tv_usec;
  }
  ut_tv;
  int32_t ut_addr_v6[4];
  char __unused[20];
}
 ;

Interfaces for libm

Table 1-28 defines the library name and shared object name for the libm library

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

Interfaces for libpthread

Table 1-31 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:

Interfaces for libgcc_s

Table 1-33 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:

Interface Definitions for libgcc_s

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

Other interfaces listed above for libgcc_s shall behave as described in the referenced base document.

_Unwind_DeleteException

_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

Interfaces for libdl

Table 1-35 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:

Interfaces for libcrypt

Table 1-37 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:

Interfaces for libz

Data Definitions for libz

This section contains standard data definitions that describe system data. 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.

ISO C serves as the LSB reference programming language, and data definitions are specified in ISO C . 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.

Interfaces for libncurses

Data Definitions for libncurses

This section contains standard data definitions that describe system data. 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.

ISO C serves as the LSB reference programming language, and data definitions are specified in ISO C . 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 int bool;

Interfaces for libutil

The behavior of the interfaces in this library is specified by the following standards.

Package Dependencies

The LSB runtime environment shall provde the following dependencies.

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

Package Architecture Considerations

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

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