General

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

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

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

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

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

Module Specific Scope

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

Interfaces described in this module are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

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.

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 Architecture is specified by the following documents

• Itanium ™ Architecture Software Developer's Manual Volume 1: Application Architecture

• Itanium ™ Architecture Software Developer's Manual Volume 2: System Architecture

• Itanium ™ Architecture Software Developer's Manual Volume 3: Instruction Set Reference

• IA-64 Processor Reference: Intel® Itanium ™ Processor Reference Manual for Software Development

• Itanium ™ Software Conventions & Runtime Architecture Guide

• Intel® Itanium ™ Processor-specific Application Binary Interface

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

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

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

There are some features of the processor architecture that need not be supported by a conforming implementation. These are described in this chapter. A conforming application shall not rely on these features.

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

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

This specification describes only LP64 (i.e. 32-bit integers, 64-bit longs and pointers) based implementations. Implementations may also provide ILP32 (32-bit integers, longs, and pointers), but conforming applications shall not rely on support for ILP32. See section 1.2 of the Intel® Itanium ™ Processor-specific Application Binary Interface for further information.

Data Representation

See Itanium ™ Software Conventions & Runtime Architecture Guide Chapter 4.

Within this specification, the term byte refers to an 8-bit object, the term halfword refers to a 16-bit object, the term word refers to a 32-bit object, the term doubleword refers to a 64-bit object, and the term quadword refers to a 128-bit object. Although the architecture also supports 120-bit addressable objects, this specification does not require LSB-conforming implementations to provide support for these objects.

---

Fundamental Types

Table 2-1 describes how fundemental C language data types shall be represented:

Table 1-1. Scalar Types

Type	C	sizeof	Alignment (bytes)	Notes
Integral	char	1	1
	signed char
	unsigned char
	short	2	2
	signed short
	unsigned short
	int	4	4
	signed int
	unsigned int
	long	8	8
	signed long
	unsigned long
	long long	8	8	See Note Below
	signed long long
	unsigned long long
Pointer	any-type *	8	8
	any-type (*)()
Floating-Point	float	4	4
	double	8	8
	long double	16	16

Support for the long long data type is dependent on support for ISO9899:1999 C language. This standard is not required for LSB-conformance, but this data type is important when developing applications for the architecture. The GNU Compiler Collection (gcc) includes support for long long of ISO9899:1999.

A null pointer (for all types) shall have the value zero.

    struct {
        char c;
    }
   

    struct {
        char  c;
        char  d;
        short s;
        int   i;
        long  l;
    }
   

    struct {
        char  c;
        long  l;
        int   i;
        short s;
    }
   

signed char
char
unsigned char
     

-2-1 to 2-1-1
0 to 2-1
0 to 2-1
     

signed short
short
unsigned short
     

-2-1 to 2-1-1
0 to 2-1
0 to 2-1
     

signed int
int
unsigned int
     

-2-1 to 2-1-1
0 to 2-1
0 to 2-1
     

signed long
long
unsigned long
     

-2-1 to 2-1-1
0 to 2-1
0 to 2-1
     

CPU Registers

The CPU general and other registers are as defined in the Itanium ™ Architecture Software Developer's Manual Volume 1: Application Architecture Section 3.1.

Floating Point Registers

The floating point registers are as defined in the Itanium ™ Architecture Software Developer's Manual Volume 1: Application Architecture Section 3.1.

Stack Frame

The stackframe layout is as described in the Itanium ™ Software Conventions & Runtime Architecture Guide Chapter 8.4.

Arguments

The procedure argument passing mechanism is as described in the Itanium ™ Software Conventions & Runtime Architecture Guide Chapter 8.5.

Return Values

See Itanium ™ Software Conventions & Runtime Architecture Guide Chapter 8.6.

Processor Execution Mode

Applications must assume that they will execute in the least privileged user mode (i.e. level 3). Other privilege levels are reserved for the Operating System.

Exception Interface

See Intel® Itanium ™ Processor-specific Application Binary Interface, section 3.3.1.

Signal Delivery

See Intel® Itanium ™ Processor-specific Application Binary Interface, section 3.3.2.

Special Registers

Intel® Itanium ™ Processor-specific Application Binary Interface, section 3.3.5, defines required register initializations for process startup.

Process Stack (on entry)

As defined in Intel® Itanium ™ Processor-specific Application Binary Interface, section 3.3.5, the return pointer register (rp) shall contain a valid return address, such that if the application program returns from the main entry routine, the implementation shall cause the application to exit normally, using the returned value as the exit status. Further, the unwind information for this "bottom of stack" routine in the implementation shall provide a mechanism for recognizing the bottom of the stack during a stack unwind.

Auxiliary Vector

The auxiliary vector conveys information from the operating system to the application. Only the terminating null auxiliary vector entry is required, but if any other entries are present, they shall be interpreted as follows. This vector is an array of the following structures.

typedef struct
{
  long int a_type;              /* Entry type */
  union
    {
      long int a_val;           /* Integer value */
      void *a_ptr;              /* Pointer value */
      void (*a_fcn) (void);     /* Function pointer value */
    } a_un;
} auxv_t;

The application shall interpret the a_un value according to the a_type. Other auxiliary vector types are reserved.

The a_type field shall contain one of the following values:

The auxiliary vector is intended for passing information from the operating system to the program interpreter.

Environment

Although a pointer to the environment vector should be available as a third argument to the main entry point, conforming applications should use getenv to access the environment. (See ISO/IEC 9945:2003 Portable Operating System(POSIX)and The Single UNIX® Specification(SUS) V3, Section exec).

Code Model Overview/Architecture Constraints

As defined in Intel® Itanium ™ Processor-specific Application Binary Interface, relocatable files, executable files, and shared object files that are supplied as part of an application must use Position Independent Code, as described in Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 12.

Position-Independent Function Prologue

See Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 8.4.

Data Objects

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.4, and Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 12.3.

Function Calls

See Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 8.4.

Four types of procedure call are defined in Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 8.3. Although special calling conventions are permitted, provided that the compiler and runtime library agree on these conventions, none are defined for this standard. Consequently, no application shall depend on a type of procedure call other than Direct Calls, Direct Dynamically Linked Calls, or Indirect Calls, as defined in Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 8.3.

Branching

Branching is described in IA-64 Processor Reference: Intel® Itanium ™ Processor Reference Manual for Software Development, Chapter 4.5.

Variable Argument List

See Itanium ™ Software Conventions & Runtime Architecture Guide, Chapter 8.5.2, and 8.5.4.

Dynamic Allocation of Stack Space

The C library alloca function should be used to dynamically allocate stack space.

Machine Information

LSB-conforming applications shall use the Machine Information as defined in Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 4. Implementations shall support the LP64 model. It is unspecified whether or not the ILP32 model shall also be supported.

Special Sections

The following sections are defined in the Intel® Itanium ™ Processor-specific Application Binary Interface.

Linux Special Sections

The following Linux IA-64 specific sections are defined here.

Section Types

Section Types are described in the Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 4.2. LSB conforming implementations are not required to use any sections in the range from SHT_IA_64_LOPSREG to SHT_IA_64_HIPSREG. Additionally, LSB conforming implementations are not required to support the SHT_IA_64_PRIORITY_INIT section, beyond the gABI requirements for the handling of unrecognized section types, linking them into a contiguous section in the object file created by the static linker.

Section Attribute Flags

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 4.2.2.

Special Section Types

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 4.2.3.

Relocation Types

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 4.3.

Types

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.1.

Flags

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.1.

Dynamic Entries

Global Offset Table

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.4.

Shared Object Dependencies

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.3.

Function Addresses

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.5.

Procedure Linkage Table

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.6.

Initialization and Termination Functions

See Intel® Itanium ™ Processor-specific Application Binary Interface, Chapter 5.3.7.

Program Interpreter/Dynamic Linker

The LSB specifies the Program Interpreter to be /lib/ld-lsb-ia64.so.2.

Interfaces for libc

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

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.2) [1]	gethostid(GLIBC_2.2) [2]	listen(GLIBC_2.2) [2]	sendmsg(GLIBC_2.2) [2]	socketpair(GLIBC_2.2) [2]
accept(GLIBC_2.2) [2]	gethostname(GLIBC_2.2) [2]	recv(GLIBC_2.2) [2]	sendto(GLIBC_2.2) [2]
bind(GLIBC_2.2) [2]	getpeername(GLIBC_2.2) [2]	recvfrom(GLIBC_2.2) [2]	setsockopt(GLIBC_2.2) [1]
bindresvport(GLIBC_2.2) [1]	getsockname(GLIBC_2.2) [2]	recvmsg(GLIBC_2.2) [2]	shutdown(GLIBC_2.2) [2]
connect(GLIBC_2.2) [2]	getsockopt(GLIBC_2.2) [2]	send(GLIBC_2.2) [2]	socket(GLIBC_2.2) [2]

Referenced Specification(s)

[1]. Linux Standard Base

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

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.2) [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.2) [1]

regerror(GLIBC_2.2) [1]

regexec(GLIBC_2.2) [1]

regfree(GLIBC_2.2) [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.2) [1]

re_comp(GLIBC_2.2) [1]

re_exec(GLIBC_2.2) [1]

step(GLIBC_2.2) [1]

Referenced Specification(s)

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

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.2) [1]

loc2(GLIBC_2.2) [1]

locs(GLIBC_2.2) [1]

Referenced Specification(s)

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

---

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.2) [1]	ctime(GLIBC_2.2) [2]	gmtime(GLIBC_2.2) [2]	localtime_r(GLIBC_2.2) [2]	ualarm(GLIBC_2.2) [2]
asctime(GLIBC_2.2) [2]	ctime_r(GLIBC_2.2) [2]	gmtime_r(GLIBC_2.2) [2]	mktime(GLIBC_2.2) [2]
asctime_r(GLIBC_2.2) [2]	difftime(GLIBC_2.2) [2]	localtime(GLIBC_2.2) [2]	tzset(GLIBC_2.2) [2]

Referenced Specification(s)

[1]. Linux Standard Base

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

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.2) [1]

Referenced Specification(s)

[1]. Linux Standard Base

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

Table 1-21. libc - Time Manipulation Data Interfaces

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

Referenced Specification(s)

[1]. Linux Standard Base

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

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	EDEADLK

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

#define LONG_MAX	0x7FFFFFFFFFFFFFFFL
#define ULONG_MAX	0xFFFFFFFFFFFFFFFFUL

#define CHAR_MAX	SCHAR_MAX
#define CHAR_MIN	SCHAR_MIN

typedef long __jmp_buf[70] __attribute__ ((aligned (16)));

struct sigaction
{
  union
  {
    sighandler_t _sa_handler;
    void (*_sa_sigaction) (int, siginfo_t *, void *);
  }
  __sigaction_handler;
  unsigned long sa_flags;
  sigset_t sa_mask;
}
 ;
#define MINSIGSTKSZ	131027
#define SIGSTKSZ	262144

struct ia64_fpreg
{
  union
  {
    unsigned long bits[2];
    long double __dummy;
  }
  u;
}
 ;

struct sigcontext
{
  unsigned long sc_flags;
  unsigned long sc_nat;
  stack_t sc_stack;
  unsigned long sc_ip;
  unsigned long sc_cfm;
  unsigned long sc_um;
  unsigned long sc_ar_rsc;
  unsigned long sc_ar_bsp;
  unsigned long sc_ar_rnat;
  unsigned long sc_ar_ccv;
  unsigned long sc_ar_unat;
  unsigned long sc_ar_fpsr;
  unsigned long sc_ar_pfs;
  unsigned long sc_ar_lc;
  unsigned long sc_pr;
  unsigned long sc_br[8];
  unsigned long sc_gr[32];
  struct ia64_fpreg sc_fr[128];
  unsigned long sc_rbs_base;
  unsigned long sc_loadrs;
  unsigned long sc_ar25;
  unsigned long sc_ar26;
  unsigned long sc_rsvd[12];
  unsigned long sc_mask;
}
 ;

typedef long ptrdiff_t;
typedef unsigned long size_t;

#define FIONREAD	0x541B
#define TIOCNOTTY	0x5422

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

#define MCL_CURRENT	1
#define MCL_FUTURE	2

struct msqid_ds
{
  struct ipc_perm msg_perm;
  time_t msg_stime;
  time_t msg_rtime;
  time_t msg_ctime;
  unsigned long __msg_cbytes;
  unsigned long msg_qnum;
  unsigned long msg_qbytes;
  pid_t msg_lspid;
  pid_t msg_lrpid;
  unsigned long __unused1;
  unsigned long __unused2;
}
 ;

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

#define SHMLBA	(1024*1024)

struct shmid_ds
{
  struct ipc_perm shm_perm;
  size_t shm_segsz;
  time_t shm_atime;
  time_t shm_dtime;
  time_t shm_ctime;
  pid_t shm_cpid;
  pid_t shm_lpid;
  unsigned long shm_nattch;
  unsigned long __unused1;
  unsigned long __unused2;
}
 ;

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;
  unsigned int pad0;
  dev_t st_rdev;
  off_t st_size;
  struct timespec st_atim;
  struct timespec st_mtim;
  struct timespec st_ctim;
  blksize_t st_blksize;
  blkcnt_t st_blocks;
  unsigned long __unused[3];
}
 ;
struct stat64
{
  dev_t st_dev;
  ino64_t st_ino;
  nlink_t st_nlink;
  mode_t st_mode;
  uid_t st_uid;
  gid_t st_gid;
  unsigned int pad0;
  dev_t st_rdev;
  off_t st_size;
  struct timespec st_atim;
  struct timespec st_mtim;
  struct timespec st_ctim;
  blksize_t st_blksize;
  blkcnt64_t st_blocks;
  unsigned long __unused[3];
}
 ;

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

typedef long int64_t;

typedef int64_t ssize_t;

#define OLCUC	0000002
#define ONLCR	0000004
#define XCASE	0000004
#define NLDLY	0000400
#define CR1	0001000
#define IUCLC	0001000
#define CR2	0002000
#define CR3	0003000
#define CRDLY	0003000
#define TAB1	0004000
#define TAB2	0010000
#define TAB3	0014000
#define TABDLY	0014000
#define BS1	0020000
#define BSDLY	0020000
#define VT1	0040000
#define VTDLY	0040000
#define FF1	0100000
#define FFDLY	0100000

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

#define IXON	0002000
#define IXOFF	0010000

#define CS6	0000020
#define CS7	0000040
#define CS8	0000060
#define CSIZE	0000060
#define CSTOPB	0000100
#define CREAD	0000200
#define PARENB	0000400
#define PARODD	0001000
#define HUPCL	0002000
#define CLOCAL	0004000
#define VTIME	5

#define ISIG	0000001
#define ICANON	0000002
#define ECHOE	0000020
#define ECHOK	0000040
#define ECHONL	0000100
#define NOFLSH	0000200
#define TOSTOP	0000400
#define ECHOCTL	0001000
#define ECHOPRT	0002000
#define ECHOKE	0004000
#define FLUSHO	0010000
#define PENDIN	0040000
#define IEXTEN	0100000

#define _SC_GR0_OFFSET	(((char *) & ((struct sigcontext *) 0)->sc_gr[0]) - (char *) 0)

typedef struct sigcontext mcontext_t;

typedef struct ucontext
{
  union
  {
    mcontext_t _mc;
    struct
    {
      unsigned long _pad[_SC_GR0_OFFSET / 8];
      struct ucontext *_link;
    }
    _uc;
  }
  _u;
}
ucontext_t;

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;
  long 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 ut_session;
  struct timeval ut_tv;
  int32_t ut_addr_v6[4];
  char __unused[20];
}
 ;

Interfaces for libm

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

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_ForcedUnwind

_Unwind_GetGR

_Unwind_GetIP

_Unwind_GetLanguageSpecificData

_Unwind_GetRegionStart

_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

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

Interfaces for libncurses

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

Interfaces for libutil

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

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-ia64.

Package Architecture Considerations

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

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