

	Home • About Us •A-Z Index• Search •

Oracle Corporation Conformance Statement

Product Standard: Internationalized System Calls and Libraries Extended V3

Organization	Oracle Corporation
Author	Jim Pugsley

1. Internationalized System Calls and Libraries Extended V3

Product Information

	Product Identification	Version/Release Number	Product Supplier
1.	Oracle Solaris Operating System on SPARC	11 FCS and later	Oracle Corporation
2.	Oracle Solaris Operating System on X86	11 FCS and later	Oracle Corporation

Environment Specification

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
1.	32-bit x86 platform; Sun Fire X4150 Operating Environment: Oracle Solaris 11	Oracle Solaris 11 Operating System on x86, 32-bit	None.	Test Report from Test Suite	Test Suite: VSX4.7.4, VSX5.3.3, VSU5.3.3, VSRT5.4.4, VSTH5.5.4 Test Report: vsx_osol11_amd64-32
2.	32-bit SPARC platform; Sun SPARC Enterprise T5220 Operating Environment: Oracle Solaris 11	Oracle Solaris 11 Operating System on SPARC, 32-bit	None.	Test Report from Test Suite	Test Suite: VSX4.7.4, VSX5.3.3, VSU5.3.3, VSRT5.4.4, VSTH5.5.4 Test Report: vsx_osol11_sparc-32
3.	64-bit x86 platform; Sun Fire X4150 Operating Environment: Oracle Solaris 11	Oracle Solaris 11 Operating System on x86, 64-bit	None.	Test Report from Test Suite	Test Suite: VSX4.7.4, VSX5.3.3, VSU5.3.3, VSRT5.4.4, VSTH5.5.4 Test Report: vsx_osol11_amd64-64
4.	64-bit SPARC platform; Sun SPARC Enterprise T5220 Operating Environment: Oracle Solaris 11	Oracle Solaris 11 Operating System on SPARC, 64-bit	None.	Test Report from Test Suite	Test Suite: VSX4.7.4, VSX5.3.3, VSU5.3.3, VSRT5.4.4, VSTH5.5.4 Test Report: vsx_osol11_sparc-64

Temporary Waivers

	Waiver Number	Expiry Date
1.	MSF.X.0110	4 November 2012

1.1 General Attributes

1.1.1 XSI Option Groups

Question 1: Which of the following XSI Option Groups are supported by the implementation?

Response

Encryption	Yes
Realtime	Yes
Advanced Realtime	No
Realtime Threads	No
Advanced Realtime Threads	No
Tracing	No
XSI STREAMS	Yes
Legacy	Yes

Support for an XSI Option Group can only be claimed if all interfaces in that group behave according to the relevant descriptions in System Interfaces, Issue 6.

If an implementation does not support an Option Group then the system need not support the functions or functional behavior.

Rationale

Base Definitions, Issue 6 states that the system may provide one or more of the XSI Option Groups listed.

1.1.2 Options

Question 2: Which of the following options are supported by the implementation?

Response

IEC 60559 Floating-Point option	Yes
IPV6	Yes
Raw Sockets	Yes

Support for these options enables additional semantics for interfaces as described in the relevant descriptions in System Interfaces, Issue 6.

Rationale

The system may provide support for additional options beyond those required for XSI conformance or covered by the XSI Option Groups.

1.1.3 POSIX.1 Supported Features

Question 3: For each of the symbolic constants, specified in the <unistd.h> header file, are the associated features always available on the system?

Response

Macro Name	Meaning	Provided
_POSIX_CHOWN_RESTRICTED	The use of chown() is restricted to a process with appropriate privileges, and to changing the group ID of a file only to the effective group ID of the process or one of its supplementary group IDs.	Yes
_POSIX_NO_TRUNC	Pathname components longer than {NAME_MAX) generate an error.	Yes

Rationale

For a conformant implementation, these POSIX features must be provided. In some cases the feature need not be provided for all files or devices supported by the implementation.

1.1.4 Float, Stdio, and Limit Values

Question 4: What are the values associated with the following constants specified in the <float.h> header file?

Response

Macro Name	Meaning	Value
FLT_RADIX	Radix of the exponent representation.	2
FLT_MANT_DIG	Number of base-FLT_RADIX digits in the float significand.	24
DBL_MANT_DIG	Number of base-FLT_RADIX digits in the double significand.	53
LDBL_MANT_DIG	Number of base-FLT_RADIX digits in the long double significand.	See Appendix
FLT_DIG	Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a float representation and back again without change to the q digits.	6
DBL_DIG	Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a double representation and back again without change to the q digits.	15
LDBL_DIG	Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a long double representation and back again without change to the q digits.	See Appendix
FLT_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised float.	-125
DBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised double.	-1021
LDBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised long double.	-16381
FLT_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised floats.	-37
DBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised doubles.	-307
LDBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised long doubles.	-4931
FLT_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite float.	128
DBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite double.	1024
LDBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite long double.	16384
FLT_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite floats.	38
DBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite doubles.	308
LDBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite long doubles.	4932
FLT_MAX	Maximum representable finite float.	3.4028234663852885981170E+38F
DBL_MAX	Maximum representable finite double.	1.7976931348623157081452E+308
LDBL_MAX	Maximum representable finite long double.	See Appendix
FLT_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a float.	1.1920928955078125000000E-07F
DBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a double.	2.2204460492503130808473E-16
LDBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a long double.	See Appendix
FLT_MIN	Minimum normalised positive float.	1.1754943508222875079688E-38F
DBL_MIN	Minimum normalised positive double.	2.2250738585072013830903E-308
LDBL_MIN	Minimum normalised positive long double.	See Appendix

Rationale

This set of constants provides useful information regarding the underlying architecture of the implementation.

Question 5: What are the values associated with the following constants (optionally specified in the <limits.h> header file)?

Response

Macro Name	Meaning	Minimum	Maximum
ARG_MAX	Maximum length of argument to the exec functions including the environment data.	4096	See Appendix
ATEXIT_MAX	Maximum number of functions that may be registered with atexit().	32	Unlimited
CHILD_MAX	Maximum number of processes per user ID.	25	Value dependent on how the system kernel is configured
FILESIZEBITS	Minimum number of bits needed to represent as a signed integer value the maximum size of a regular file.	32	41
HOST_NAME_MAX	Maximum length of a host name as returned from gethostname().	255	255
IOV_MAX	Maximum number of iovec structures that one process has available for use with readv() or writev().	16	16
LINK_MAX	Maximum number of links to a single file.	8	32767
LOGIN_NAME_MAX	Maximum length of a login name.	9	9
MAX_CANON	Maximum number of bytes in a terminal canonical input line.	255	256
MAX_INPUT	Maximum number of bytes for which space will be available in a terminal input queue.	255	512
NAME_MAX	Maximum number of bytes in a filename (not including terminating null).	14	The maximum value for NAME_MAX varies depending on the file system type, but always provides at least the minimum requirement. The most common value is 255. Values for a specific path are available using pathconf()
OPEN_MAX	Maximum number of open files that one process can have open at any one time.	20	256
PAGESIZE	Size of a page in bytes.	1	Variable
PAGE_SIZE	Same as PAGESIZE. If either PAGESIZE or PAGE_SIZE is defined, the other will be defined with the same value.	1	Variable
PATH_MAX	Maximum number of bytes in a pathname (including the terminating null).	255	The maximum value for PATH_MAX varies depending on the file system type, but always provides at least the minimum requirement. The most common value is 1024. Values for a specific path are available using pathconf().
PIPE_BUF	Maximum number of bytes that is guaranteed to be atomic when writing to a pipe.	512	5120
PTHREAD_DESTRUCTOR_ITERATIONS	Maximum number of attempts made to destroy a thread's thread-specific data values on thread exit.	4	Variable
PTHREAD_KEYS_MAX	Maximum number of data keys that can be created by a process.	128	Variable
PTHREAD_STACK_MIN	Minimum size in bytes of thread stack storage.	0	Variable
PTHREAD_THREADS_MAX	Maximum number of threads that can be created by a process.	64	Variable
STREAM_MAX	Number of streams that one process can have open at one time.	8	256
SYMLINK_MAX	Number of bytes in a symbolic link.	255	1024
SYMLOOP_MAX	Number of symbolic links that can be reliably traversed in the resolution of a pathname in the absence of a loop.	8	20
TTY_NAME_MAX	Maximum length of terminal device name.	9	128
TZNAME_MAX	Maximum number of bytes supported for the name of a time zone.	6	6

Rationale

Each of these limits can vary within bounds set by the Base Definitions, Issue 6. The minimum permitted value is specified in Chapter 13, <limits.h>.

Question 6: What are the values associated with the following constants specified in the <limits.h> header file?

Response

For each line in the table below, add the minimum and maximum values for your implementation. These values may be stated to be "Unlimited" if your implementation does not impose a limit. The minimum should be the smallest value that is returned from sysconf(), pathconf(), or fpathconf(), or as defined in <limits.h>. The maximum value should be the largest value that is returned from sysconf(), pathconf(), or fpathconf().

Macro Name	Meaning	Minimum	Maximum
BC_BASE_MAX	Maximum ibase and obase values allowed by the bc utility.	99	99
BC_DIM_MAX	Maximum number of elements permitted in an array by the bc utility.	2048	2048
BC_SCALE_MAX	Maximum scale value allowed by the bc utility.	99	99
BC_STRING_MAX	Maximum length of a string constant accepted by the bc utility.	1000	1000
CHARCLASS_NAME_MAX	Maximum number of bytes in a character class name.	14	14
COLL_WEIGHTS_MAX	Maximum number of weights that can be assigned to an entry of the LC_COLLATE order keyword in the locale definition file.	2	10
EXPR_NEST_MAX	Maximum number of expressions that can be nested within parentheses by the expr utility.	32	32
LINE_MAX	Maximum length in bytes including the trailing newline of a utility's input line when the utility is described as processing text files.	2048	2048
NGROUPS_MAX	Maximum number of simultaneous supplementary group IDs per process.	8	16
RE_DUP_MAX	Maximum number of repeated occurrences of a regular expression permitted when using interval notation.	255	255

Rationale

Each of these limits can vary within bounds set by the Base Definitions, Issue 6. The minimum value that a limit can take on any conforming system is given in the corresponding _POSIX_ or _POSIX2_ value. A specific conforming implementation may provide a higher minimum value than this and the maximum value that it provides can differ from the minimum. Some conforming implementations may provide a potentially infinite value as the maximum, in which case the value is considered to be indeterminate. The minimum value must always be definitive since the _POSIX_ or _POSIX2_ value provides a known lower bound for the range of possible values.

Question 7: What are the values associated with the following numerical constants specified in the <limits.h> header file?

Response

Macro Name	Meaning	Value
CHAR_MAX	Maximum value of a char.	127
INT_MAX	Maximum value of an int.	2147483647
LONG_BIT	Number of bits in a long int.	See Appendix
LONG_MAX	Maximum value of a long int.	See Appendix
LLONG_MAX	Maximum value of a long long.	9223372036854775807LL
MB_LEN_MAX	Maximum number of bytes in a character, for any supported locale.	5
SHRT_MAX	Maximum value of a short.	32767
SSIZE_MAX	Maximum value of an object of type ssize_t.	See Appendix
UINT_MAX	Maximum value of an unsigned int.	4294967295U
ULONG_MAX	Maximum value of an unsigned long int.	See Appendix
ULLONG_MAX	Maximum value of a unsigned long long.	18446744073709551615LL
USHRT_MAX	Maximum value of an unsigned short int.	65535
WORD_BIT	Number of bits in a word or int.	32

Rationale

This set of constants provides useful information regarding the underlying architecture of the implementation.

Question 8: What are the values associated with the following numerical constants specified in the <stdio.h> header file?

Response

Macro Name	Meaning	Value
FILENAME_MAX	Maximum size in bytes of the longest filename string that the implementation guarantees can be opened.	1024
FOPEN_MAX	Number of streams which the implementation guarantees can be open simultaneously.	60
L_ctermid	Maximum size of character array to hold ctermid() output.	9
L_tmpnam	Maximum size of character array to hold tmpnam() output.	25
TMP_MAX	Minimum number of unique filenames generated by tmpnam(), which is the maximum number of times an application can call tmpnam() reliably.	17576

Rationale

This set of constants provides useful information about the implementation.

1.1.5 Error Conditions

Question 9: Which of the following option errors, ( denoted by "may fail" within the specification ), listed in System Interfaces, Issue 6 are detected in the circumstances specified?

Response

Function	Error	Detected
accept()	EINVAL	No
	ENOMEM	Yes
	EPROTO	Yes
access()	EINVAL	Yes
	ENAMETOOLONG	Yes
	ETXTBSY	No
asin() *	Range Error	No
asinh() *	Range Error	No
atan() *	Range Error	No
atanh() *	Range Error	No
atan2() *	Range Error	No
bind()	EACCESS	Yes
	EINVAL	Yes
	EISCONN	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOBUFS	Yes
catclose()	EBADF	Yes
catclose()	EINTR	Yes
catgets()	EBADF	Yes
	EBADMSG	Yes
	EINTR	Yes
	EINVAL	No
	ENOMSG	Yes
catopen()	EACCES	Yes
	EMFILE	Yes
	ENAMETOOLONG	Yes
	ENFILE	Yes
	ENOENT	Yes
	ENOMEM	Yes
	ENOTDIR	Yes
cfsetispeed()	EINVAL	No
cfsetospeed()	EINVAL	No
chdir()	ENAMETOOLONG	Yes
chdir()	ELOOP	Yes
chmod()	EINTR	No
	EINVAL	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
chown()	EINTR	Yes
	EINVAL	Yes
	EIO	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
close()	EIO	Yes
closedir()	EBADF	Yes
closedir()	EINTR	No
connect()	EACCESS	Yes
	EADDRINUSE	Yes
	ECONNRESET	Yes
	EHOSTUNREACH	Yes
	EINVAL	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENETDOWN	Yes
	ENOBUFS	Yes
	EOPNOTSUP	Yes
endpwent()	EIO	Yes
erf() *	Range Error	No
erfc() *	Range Error	No
exec	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOMEM	No
	ETXTBSY	No
exp() *	Range Error	No
exp2() *	Range Error	No
expm1() *	Range Error	No
fchdir()	EINTR	Yes
fchdir()	EIO	Yes
fchmod()	EINTR	Yes
fchmod()	EINVAL	Yes
fchown()	EINVAL	Yes
	EIO	Yes
	EINTR	Yes
fclose()	ENXIO	Yes
fcntl()	EDEADLK	Yes
fdim() *	Range Error	Yes
fdopen()	EBADF	No
	EINVAL	No
	EMFILE	Yes
	ENOMEM	Yes
fflush()	ENXIO	Yes
fgetc()	ENOMEM	Yes
fgetc()	ENXIO	Yes
fgetpos()	EBADF	Yes
fgetpos()	ESPIPE	Yes
fgetwc()	ENOMEM	Yes
fgetwc()	ENXIO	Yes
fileno()	EBADF	No
fma() *	Domain Error	Yes
fma() *	Range Error	No
fmod() *	Range Error	No
fopen()	EINVAL	Yes
	ELOOP	Yes
	EMFILE	Yes
	ENAMETOOLONG	Yes
	ENOMEN	Yes
	ETXTBSY	No
fork()	ENOMEM	Yes
fpathconf()	EBADF	Yes
fpathconf()	EINVAL	Yes
fprintf()	EINVAL	Yes
	EILSEQ	Yes
	ENOMEM	Yes
fputc()	ENOMEM	Yes
fputc()	ENXIO	Yes
fputwc()	ENOMEM	Yes
fputwc()	ENXIO	Yes
fread()	ENOMEM	No
fread()	ENXIO	No
freopen()	EINVAL	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOMEM	Yes
	ENXIO	Yes
	ETXTBSY	No
fscanf()	EILSEQ	Yes
	EINVAL	Yes
	ENOMEM	Yes
	ENXIO	Yes
fstat()	EOVERFLOW	Yes
ftell()	ESPIPE	Yes
ftok()	ELOOP	Yes
ftok()	ENAMETOOLONG	Yes
ftw()	EINVAL	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
fwide()	EBADF	Yes
fwprintf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
	EINVAL	Yes
fwscanf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
	EINVAL	Yes
getcwd()	EACCES	Yes
getcwd()	ENOMEM	Yes
getgrent()	EINTR	No
	EIO	Yes
	EMFILE	Yes
	ENFILE	Yes
getgrgid()	EIO	Yes
	EINTR	No
	EMFILE	Yes
	ENFILE	Yes
getgrgid_r()	ERANGE	Yes
getgrnam()	EIO	Yes
	EINTR	No
	EMFILE	Yes
	ENFILE	Yes
getgrnam_r()	ERANGE	Yes
getitimer()	EINVAL	Yes
getlogin()	EMFILE	Yes
	ENFILE	Yes
	ENXIO	Yes
getlogin_r()	ERANGE	Yes
getpeername()	ENOBUFS	Yes
getpgid()	EINVAL	Yes
getpwent()	EIO	Yes
	EMFILE	Yes
	ENFILE	Yes
getpwnam()	EIO	Yes
	EINTR	No
	EMFILE	Yes
	ENFILE	Yes
getpwnam_r()	ERANGE	Yes
getpwuid()	EIO	Yes
	EINTR	No
	EMFILE	Yes
	ENFILE	Yes
getpwuid_r()	ERANGE	Yes
getsockname()	EINVAL	Yes
getsockname()	ENOBUFS	Yes
getsockopt()	EACCESS	Yes
	EINVAL	Yes
	ENOBUFS	Yes
grantpt()	EBADF	Yes
	EINVAL	Yes
	EACCES	Yes
hcreate()	ENOMEM	Yes
hsearch()	ENOMEM	Yes
hypot() *	Range Error	No
iconv()	EBADF	Yes
iconv_close()	EBADF	Yes
iconv_open()	EMFILE	Yes
	ENFILE	Yes
	ENOMEM	Yes
	EINVAL	Yes
if_nameindex()	ENOBUFS	No
isatty()	EBADF	No
isatty()	ENOTTY	No
j0()	Range Error	No
j1()	Range Error	No
jn()	Range Error	No
lchown()	EIO	Yes
	EINTR	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
ldexp() *	Range Error	No
link()	ELOOP	Yes
link()	ENAMETOOLONG	Yes
listen()	EACCESS	No
	EINVAL	Yes
	ENOBUFS	Yes
lockf()	EAGAIN	Yes
	EDEADLK	Yes
	EINVAL	Yes
	ENOLCK	Yes
	EOPNOTSUPP	Yes
log1p() *	Range Error	No
lstat()	ELOOP	Yes
	ENAMETOOLONG	Yes
	EOVERFLOW	Yes
mblen()	EILSEQ	Yes
mbrlen()	EINVAL	No
mbrlen()	EILSEQ	Yes
mbrtowc()	EINVAL	No
mbrtowc()	EILSEQ	Yes
mbsrtowcs()	EINVAL	No
mbsrtowcs()	EILSEQ	Yes
mbstowcs()	EILSEQ	Yes
mbtowc()	EILSEQ	Yes
mkdir()	ELOOP	Yes
mkdir()	ENAMETOOLONG	Yes
mkfifo()	ELOOP	Yes
mkfifo()	ENAMETOOLONG	Yes
mknod()	ELOOP	Yes
mknod()	ENAMETOOLONG	No
nftw()	ELOOP	Yes
	EMFILE	Yes
	ENAMETOOLONG	Yes
	ENFILE	Yes
open()	EAGAIN	Yes
	EINVAL	No
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOMEM	Yes
	ETXTBSY	No
opendir()	ELOOP	Yes
	EMFILE	Yes
	ENAMETOOLONG	Yes
	ENFILE	Yes
pathconf()	EACCES	Yes
	EINVAL	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOENT	Yes
	ENOTDIR	Yes
popen()	EMFILE	Yes
popen()	EINVAL	No
posix_openpt()	EINVAL	Yes
posix_openpt()	EAGAIN	Yes
pow() *	Range Error	No
pread()	ENXIO	Yes
printf()	ENOMEM	Yes
pthread_attr_setstack()	EACCESS	No
pthread_attr_setstack()	EINVAL	Yes
pthread_cancel()	ESRCH	Yes
pthread_cond_broadcast()	EINVAL	No
pthread_cond_destroy()	EBUSY	No
pthread_cond_destroy()	EINVAL	No
pthread_cond_init()	EBUSY	No
pthread_cond_init()	EINVAL	Yes
pthread_cond_signal()	EINVAL	No
pthread_cond_timedwait()	EINVAL	Yes
pthread_cond_wait()	EINVAL	No
pthread_condattr_destroy()	EINVAL	Yes
pthread_condattr_setpshared()	EINVAL	Yes
pthread_join()	EDEADLK	Yes
pthread_key_delete()	EINVAL	Yes
pthread_mutex_destroy()	EBUSY	No
pthread_mutex_destroy()	EINVAL	No
pthread_mutex_init()	EBUSY	No
pthread_mutex_init()	EINVAL	No
pthread_mutex_lock()	EINVAL	Yes
	EAGAIN	Yes
	EDEADLK	Yes
pthread_mutex_trylock()	EINVAL	Yes
pthread_mutex_trylock()	EAGAIN	Yes
pthread_mutex_unlock()	EINVAL	No
	EAGAIN	Yes
	EPERM	Yes
pthread_mutexattr_destroy()	EINVAL	Yes
pthread_mutexattr_gettype()	EINVAL	Yes
pthread_mutexattr_init()	ENOMEM	Yes
pthread_mutexattr_setpshared()	EINVAL	Yes
pthread_mutexattr_settype()	EINVAL	Yes
pthread_once()	EINVAL	Yes
pthread_rwlock_destroy()	EBUSY	No
pthread_rwlock_destroy()	EINVAL	No
pthread_rwlock_init()	EBUSY	No
pthread_rwlock_init()	EINVAL	Yes
pthread_rwlock_rdlock()	EINVAL	No
	EDEADLK	Yes
	EAGAIN	Yes
pthread_rwlock_tryrdlock()	EINVAL	No
pthread_rwlock_tryrdlock()	EAGAIN	Yes
pthread_rwlock_trywrlock()	EINVAL	No
pthread_rwlock_unlock()	EINVAL	No
pthread_rwlock_unlock()	EPERM	Yes
pthread_rwlock_wrlock()	EINVAL	No
pthread_rwlock_wrlock()	EDEADLK	Yes
pthread_rwlockattr_destroy()	EINVAL	Yes
pthread_rwlockattr_setpshared()	EINVAL	Yes
pthread_setcancelstate()	EINVAL	Yes
pthread_setcanceltype()	EINVAL	Yes
pthread_setspecific()	EINVAL	Yes
putc()	ENOMEM	Yes
putc()	ENXIO	Yes
putchar()	ENOMEM	Yes
putchar()	ENXIO	Yes
putenv()	ENOMEM	Yes
puts()	ENOMEM	No
puts()	ENXIO	No
pututxline()	EPERM	Yes
putwc()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
putwchar()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
pwrite()	EINVAL	Yes
pwrite()	ENXIO	Yes
read()	EIO	Yes
	ENOBUFS	No
	ENOMEM	No
	ENXIO	Yes
readdir()	EBADF	Yes
readdir()	ENOENT	Yes
readdir_r()	EBADF	Yes
readlink()	EACCES	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
readv()	EINVAL	Yes
realpath()	ELOOP	Yes
	ENAMETOOLONG	Yes
	ENOMEM	Yes
recv()	EIO	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
recvfrom()	EIO	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
recvmsg()	EIO	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
remove()	EBUSY	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ETXTBSY	No
rename()	EBUSY	Yes
	ELOOP	Yes
	ENAMETOOLONG	Yes
	ETXTBSY	No
rmdir()	ELOOP	Yes
rmdir()	ENAMETOOLONG	Yes
round() *	Range Error	No
scalb() *	Range Error	No
send()	EACCESS	No
	EIO	Yes
	ENETDOWN	Yes
	ENETUNREACH	Yes
	ENOBUFS	Yes
sendmsg()	EACCESS	Yes
	EDESTADDRREQ	Yes
	EHOSTUNREACH	Yes
	EIO	Yes
	EISCONN	Yes
	ENETDOWN	Yes
	ENETUNREACH	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
sendto()	EACCESS	Yes
	EDESTADDRREQ	Yes
	EHOSTUNREACH	Yes
	EIO	Yes
	EISCONN	Yes
	ENETDOWN	Yes
	ENETUNREACH	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
setitimer()	EINVAL	Yes
setpriority()	EPERM	Yes
setpriority()	EACCES	Yes
setpwent()	EIO	Yes
	EMFILE	Yes
	ENFILE	Yes
setrlimit()	EINVAL	Yes
setsockopt()	ENOMEM	Yes
setsockopt()	ENOBUFS	Yes
setvbuf()	EBADF	No
shmctl()	EOVERFLOW	Yes
shutdown()	ENOBUFS	Yes
sigaction()	EINVAL	Yes
sigaddset()	EINVAL	Yes
sigdelset()	EINVAL	Yes
sigismember()	EINVAL	Yes
signal()	EINVAL	Yes
sigwait()	EINVAL	Yes
sin() *	Range Error	No
sinh() *	Range Error	No
socket()	EACCESS	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
socketpair()	EACCESS	Yes
	ENOBUFS	Yes
	ENOMEM	Yes
stat()	ELOOP	Yes
	ENAMETOOLONG	Yes
	EOVERFLOW	Yes
statvfs()	ELOOP	Yes
statvfs()	ENAMETOOLONG	Yes
strcoll()	EINVAL	No
strdup()	ENOMEM	Yes
strerror()	EINVAL	Yes
strerror_r()	ERANGE	Yes
strtod()	EINVAL	No
strtoimax()	EINVAL	Yes
strtol()	EINVAL	Yes
strtoumax()	EINVAL	Yes
strtoul()	EINVAL	Yes
strxfrm()	EINVAL	No
swprintf()	EILSEQ	Yes
swprintf()	EINVAL	Yes
swcsanf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
symlink()	ELOOP	Yes
symlink()	ENAMETOOLONG	Yes
system()	ECHILD	Yes
tan() *	Range Error	No
tanh() *	Range Error	No
tcdrain()	EIO	Yes
tcflow()	EIO	Yes
tcflush()	EIO	Yes
tcsendbreak()	EIO	Yes
tcsetattr()	EIO	Yes
tmpfile()	EMFILE	Yes
tmpfile()	ENOMEM	Yes
towctrans()	EINVAL	No
truncate()	ELOOP	Yes
truncate()	ENAMETOOLONG	Yes
ttyname()	EBADF	Yes
ttyname()	ENOTTY	Yes
ttyname_r()	EBADF	Yes
	ENOTTY	Yes
	ERANGE	Yes
ungetwc()	EILSEQ	Yes
unlink()	EBUSY	Yes
	ELOOP	No
	ENAMETOOLONG	Yes
	ETXTBSY	No
unlockpt()	EBADF	Yes
unlockpt()	EINVAL	Yes
usleep()	EINVAL	Yes
utime()	ELOOP	Yes
utime()	ENAMETOOLONG	Yes
utimes()	ELOOP	Yes
utimes()	ENAMETOOLONG	Yes
vfscanf()	EILSEQ	Yes
	EINVAL	Yes
	ENOMEM	Yes
	ENXIO	Yes
vfwprintf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
	EINVAL	Yes
vfwscanf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
	EINVAL	Yes
wcrtomb()	EINVAL	No
wcrtomb()	EILSEQ	Yes
wcscoll()	EINVAL	Yes
wcsrtombs()	EINVAL	No
wcsrtombs()	EILSEQ	Yes
wcstod()	EINVAL	Yes
wcstoimax()	EINVAL	Yes
wcstoumax()	EINVAL	Yes
wcstol()	EINVAL	Yes
wcstombs()	EILSEQ	Yes
wcstoul()	EINVAL	Yes
wcsxfrm()	EINVAL	Yes
wctrans()	EINVAL	No
wprintf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
	EINVAL	Yes
write()	EINVAL	Yes
	ENETDOWN	No
	ENETUNREACH	No
	ENXIO	Yes
writev()	EINVAL	Yes
wscanf()	ENOMEM	Yes
	ENXIO	Yes
	EILSEQ	Yes
y0()	Domain Error	No
y0()	Range Error	No
y1()	Domain Error	No
y1()	Range Error	No
yn()	Domain Error	No
yn()	Range Error	No

Rationale

Each of the above error conditions is marked as optional in System Interfaces, Issue 6 and an implementation may return this error in the circumstances specified or may not provide the error indication.

1.1.6 Mathematical Interfaces

Question 10: What format of floating-point numbers is supported by this implementation?

Response

IEEE floating-point format.

Rationale

Most implementations support IEEE floating-point format either in hardware or software. Some implementations support other formats with different exponent and mantissa accuracy. These differences need to be defined.

Question 11: Which floating-point exceptions are supported by this implementation for the fegetexecptflag(), feraiseexcept(), fesetexecptflag(), and fetestexecptflag() functions?

Response

FE_DIVBYZERO, FE_INEXACT, FE_INVALID, FE_OVERFLOW, FE_UNDERFLOW

Rationale

The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.

Question 12: Which floating-point rounding directions are supported by this implementation for the fegetround(), and fesetround() functions?

Response

FE_DOWNWARD, FE_TONEAREST, FE_TOWARDZERO, FE_UPWARD

Rationale

The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.

Question 13: Is a non-stop floating-point exception mode supported by this implementation?

Response

Yes

Rationale

The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.

1.1.7 Data Encryption

Question 14: Are the optional data encryption interfaces provided?

Response

Function	Provided
crypt()	Yes
encrypt()	Yes
setkey()	Yes

Export Restrictions:

Decryption capabilities are not provided to areas restricted by U.S. export law.

Rationale

Normally, an implementation will either provide all three of these routines or will provide none of them at all. If the routines are not provided, then the implementation must provide a dummy interface which always raises an ENOSYS error condition.

It is also possible that the implementation of the encrypt() function may be affected by export restrictions, in which case, the restrictions should be documented here.

For example, historical implementations have supplied all three of these routines outside the U.S.A., but due to export restrictions on the decoding algorithm, a dummy version of encrypt() is provided that does encoding but no decoding.

1.2 Process Handling

1.2.1 Process Generation

Question 15: Which file types (regular, directory, FIFO, special and so on) are considered to be executable?

Response

Only regular files may be executed.

Rationale

The EACCES error associated with exec functions occurs in circumstances when the implementation does not support execution of files of the type specified. A list of these file types needs to be provided.

1.3 File Handling

1.3.1 Access Control

Question 16: What file access control mechanisms does the implementation provide?

Response

Oracle Solaris provides access control lists, which are an alternate access control mechanism.

Rationale

System Interfaces, Issue 6 notes that implementations may provide additional or alternate file access control mechanisms, or both.

1.3.2 Files and Directories

Question 17: Are any additional or alternate file access control mechanisms implemented that could cause fstat() or stat() to fail?

Response

Yes

Rationale

System Interfaces, Issue 6 notes that there could be an interaction between additional and alternate access controls and the success of fstat() and stat(). This would suggest that an implementation can allow access to a file but not allow the process to gain information about the status of the file.

1.4 Internationalized System Interfaces

1.4.1 Coded Character Sets

Question 18: What coded character sets are supported by the implementation?

Response

View Character Sets

Rationale

Base Definitions, Issue 6 states that conforming implementations support one or more coded character sets, and that each of these includes the portable character set.

Question 19: What is the implementation's underlying internal codeset?

Response

Information about the underlying codeset is not public because it is subject to change. Applications should use only those APIs provided by XSH6 and should avoid direct dependencies on the implementation.

Rationale

It is useful to be aware of the underlying codeset of the implementation.

1.5 Pseudo-Terminals

1.5.1 Master close

Question 20: Does closing the master side of a pseudo-terminal flush all queued input and output?

Response

Yes

Rationale

The behaviour of a conforming implementation in this area is not mandated in the specification and needs to be defined.

1.5.2 Slave close

Question 21: Does closing the slave side of a pseudo-terminal cause a zero-length message to be sent to the master?

Response

Yes

Rationale

The behaviour of a conforming implementation in this area is not mandated in the specification and needs to be defined.

1.5.3 Naming Conventions

Question 22: What naming conventions are associated with the master side of pseudo-terminal devices?

Response

/dev/pty[p-r][0-9a-f] controller (master) devices /dev/tty[p-r][0-9a-f] slave devices

Rationale

This information is not specified in System Interfaces, Issue 6, and needs to be defined.

1.6 Polling

Question 23: What types of file can be polled?

Response

Regular files, Terminals, Pseudo-Terminals, STREAMS, Sockets, FIFOs, Pipes

Rationale

Conformance requires that the poll() function supports regular files, terminals, pseudo-terminals, STREAMS, sockets, FIFOs, and pipes. The behaviour of poll() with regards to other file types needs to be defined.

1.7 Stack Growth Direction

Question 24: What is the direction of stack growth?

Response

Rationale

The specification does not define the direction of stack growth but an application needs this information to define an alternate stack for signals.

1.8 Signal Codes

Question 25: Which of the following si_code values may be generated?

Response

Signal	Code	Generated?
SIGILL	ILL_ILLOPC	Yes
	ILL_ILLOPN	Yes
	ILLL_ILLADR	Yes
	ILL_ILLTRP	Yes
	ILL_PRVOPC	Yes
	ILL_PRVREG	Yes
	ILL_COPROC	Yes
	ILL_BADSTK	Yes
SIGFPE	FPE_INTDIV	Yes
	FPE_INTOVF	Yes
	FPE_FLTDIV	Yes
	FPE_FLTOVF	Yes
	FPE_FLTUND	Yes
	FPE_FLTRES	Yes
	FPE_FLTINV	Yes
	FPE_FLTSUB	Yes
SIGSEGV	SEGV_MAPERR	Yes
SIGSEGV	SEGV_ACCERR	Yes
SIGBUS	BUS_ADRALN	Yes
	BUS_ADRERR	Yes
	BUS_OBJERR	Yes
SIGTRAP	TRAP_BRKPT	Yes
SIGTRAP	TRAP_TRACE	Yes
SIGCHLD	CLD_EXITED	Yes
	CLD_KILLED	Yes
	CLD_DUMPED	Yes
	CLD_TRAPPED	Yes
	CLD_STOPPED	Yes
	CLD_CONTINUED	Yes
SIGPOLL	POLL_IN	Yes
	POLL_OUT	Yes
	POLL_MSG	Yes
	POLL_ERR	Yes
	POLL_PRI	Yes
	POLL_HUP	Yes
Any	SI_USER	Yes
	SI_QUEUE	Yes
	SI_TIMER	Yes
	SI_ASYNCIO	Yes
	SI_MESGQ	Yes

Rationale

An Internationalized System Calls and Libraries Extended V3 conformant system may contain limitations that prevent some of the above values from being generated.

1.9 Set Process Group ID

Question 26: Does the setpgrp() function create a new session?

Response

Yes

Rationale

It is unspecified whether or not a successful call to the setpgrp() function will cause a new session to be created.

1.10 Signals Generating a Core File

Question 27: Does the implementation generate a core file when the following signals are delivered to a process?

Response

Signal	Core File Generated
SIGABRT	Yes
SIGFPE	Yes
SIGILL	Yes
SIGQUIT	Yes
SIGSEGV	Yes
SIGBUS	Yes
SIGSYS	Yes
SIGTRAP	Yes
SIGXCPU	Yes
SIGXFSZ	Yes

Rationale

Implementation-defined actions, such as creation of a core file, may occur on abnormal termination of a process.

1.11 Sockets

1.11.1 Listen Queues

Question 28: What is the limit the implementation places on the length of a socket's listen queue?

Response

None

Rationale

The specification states that an implementation may limit the length of a socket's listen queue, and that this limit may be imposed if the setting of the backlog argument exceeds an implementation-defined maximum value.

1.11.2 Address Families, Socket Types, and Protocols

Question 29: What combinations of address family, socket types, and protocols does the implementation support?

Response

Address Family	Protocol	Socket Type	Supported?
AF_UNIX	N/A	STREAM	Yes
AF_UNIX	N/A	SEQPACKET	Yes
AF_UNIX	N/A	DGRAM	Yes
AF_INET	TCP	STREAM	Yes
AF_INET	UDP	DGRAM	Yes
AF_INET6	TCP	STREAM	Yes
AF_INET6	UDP	DGRAM	Yes

Rationale

The specification states that the domains, socket types and protocols supported by a conforming system are implementation-defined. The Internationalized System Calls and Libraries Extended V3 Product Standard states that conforming products shall be available in configurations that support at least following socket domains:

AF_INET, with at least SOCK_STREAM and SOCK_DGRAM socket types
AF_UNIX, with at least the SOCK_STREAM socket type.

1.11.3 Socket Types

Question 30: What socket types does the implementation support?

Response

SOCK_RAW, SOCK_STREAM, SOCK_SEQPACKET, SOCK_DGRAM

Rationale

The specification states that there are four socket types defined - SOCK_RAW, SOCK_STREAM, SOCK_SEQPACKET and SOCK_DGRAM - but does not state which are required. Implementations may also support additional socket types.

1.12 Threads

1.12.1 Cancellation Points

Question 31: Which functions have cancellation points that occur when a thread is executing?

Response

Function	Cancellation Point?
catclose()	No
catgets()	No
catopen()	No
closedir()	No
closelog()	No
ctermid()	No
dbm_close()	No
dbm_delete()	No
dbm_fetch()	No
dbm_nextkey()	No
dbm_open()	No
dbm_store()	No
dlclose()	No
dlopen()	No
endgrent()	No
endhostent()	No
endnetent()	No
endprotoent()	No
endpwent()	No
endservent()	No
endutxent()	No
fclose()	No
fcntl()	Yes
fflush()	No
fgetc()	No
fgetpos()	No
fgets()	No
fgetwc()	No
fgetws()	No
fopen()	No
fprintf()	No
fputc()	No
fputs()	No
fputwc()	No
fputws()	No
fread()	No
freopen()	No
fscanf()	No
fseek()	No
fseeko()	No
fsetpos()	No
ftell()	No
ftello()	No
ftw()	No
fwprintf()	No
fwrite()	No
fwscanf()	No
getc()	No
getc_unlocked()	No
getchar()	No
getchar_unlocked()	No
getcwd()	No
getdate()	No
getgrent()	No
getgrgid()	No
getgrgid_r()	No
getgrnam()	No
getgrnam_r()	No
gethostbyaddr()	No
gethostbyname()	No
gethostent()	No
gethostname()	No
getlogin()	No
getlogin_r()	No
getnetbyaddr()	No
getnetbyname()	No
getnetent()	No
getprotobyname()	No
getprotobynumber()	No
getprotoent()	No
getpwent()	No
getpwnam()	No
getpwnam_r()	No
getpwuid()	No
getpwuid_r()	No
gets()	No
getservbyname()	No
getservbyport()	No
getservent()	No
getutxent()	No
getutxid()	No
getutxline()	No
getwc()	No
getwchar()	No
getwd()	No
glob()	No
iconv_close()	No
iconv_open()	No
ioctl()	No
lseek()	No
mkstemp()	No
nftw()	No
opendir()	No
openlog()	No
pclose()	No
perror()	No
popen()	No
printf()	No
pthread_rwlock_rdlock()	No
pthread_rwlock_wrlock()	No
putc()	No
putc_unlocked()	No
putchar()	No
putchar_unlocked()	No
puts()	No
pututxline()	No
putwc()	No
putwchar()	No
readdir()	No
readdir_r()	No
remove()	No
rename()	No
rewind()	No
rewinddir()	No
scanf()	No
seekdir()	No
semop()	No
setgrent()	No
sethostent()	No
setnetent()	No
setprotoent()	No
setpwent()	No
setutxent()	No
strerror()	No
syslog()	No
tmpfile()	No
tmpnam()	No
ttyname()	No
ttyname_r()	No
ungetc()	No
ungetwc()	No
unlink()	No
vfprintf()	No
vfwprintf()	No
vprintf()	No
vwprintf()	No
wprintf()	No
wscanf()	No

Rationale

Base Definitions, Issue 6 states that a cancellation point may occur for these functions.

1.13 C-language Compilation Environment

Question 32: What C-language compilation environments are provided?

Response

Programming Environment	Provided
The implementation provides a C-language compilation environment with 32-bit int, long, pointer and off_t types.	Yes
The implementation provides a C-language compilation environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits.	Yes
The implementation provides a C-language compilation environment with 32-bit int, and 64-bit long, pointer and off_t types.	Yes
The implementation provides a C-language compilation environment with int using at least 32-bits, and long, pointer and off_t types using at least 64 bits.	Yes

Rationale

Base Definitions, Issue 6 defines these scenarios as possible C-language compilation environment offerings.

Question 33: What execution environments are provided on the system under test?

Response

Execution Environment	Provided
The implementation provides an execution environment with 32-bit int, long, pointer and off_t types.	Yes
The implementation provides an execution environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits.	Yes
The implementation provides an execution environment with 32-bit int, and 64-bit long, pointer and off_t types.	Yes
The implementation provides an execution environment with int using at least 32-bits, and long, pointer and off_t types using at least 64 bits.	Yes

Rationale

Base Definitions, Issue 6 defines four scenarios as possible C-language compilation environment offerings but does not define which corresponding execution environments are supported.

1.14 Realtime

1.14.1 Prioritized I/O

Question 34: Does the implementation support _POSIX_PRIORITIZED_IO?

Response

The system does not support _POSIX_PRIORITIZED_IO.

Rationale

Support for _POSIX_PRIORITIZED_IO is optional.

1.14.2 Cancelable Asynchronous I/O Operations

Question 35: If the Realtime Option Group is supported, what asynchronous I/O operations are cancelable with aio_cancel()?

Response

aio_read(), aio_write(), and aio_fsync() are all cancelable.

Rationale

The operations which are cancelable are implementation-defined.

1.15 Realtime Threads

1.15.1 Scheduling Policies

Question 36: If the Realtime Threads Option Group is supported, what scheduling policy is associated with SCHED_OTHER?

Response

Not Applicable

Rationale

Base Definitions, Issue 6 states that conforming implementations must support a scheduling policy identified as SCHED_OTHER but define its effects as implementation-defined.

1.15.2 Scheduling Contention Scope

Question 37: If the Realtime Threads Option Group is supported, what scheduling contention scopes are supported: PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both?

Response

Rationale

System Interfaces, Issue 6 states that conforming implementations will support PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both.

1.15.3 Default Scheduling Contention Scope

Question 38: If the Realtime Threads Option Group is supported, what is the default scheduling contention scope when a process is created?

Response

Rationale

The specification defines the default scheduling contention scope as implementation-defined.

2. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.

View Appendix

3. Change History

Date	Name	Comment
08-Nov-2011	Open Brand Cert Authority	Added Appendix / Charset files
10-Oct-2011	Jim Pugsley	Document creation.

The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.

[ Home ] [ The Open Brand ] [ Conformance Statement Library ] [ Search Conformance Statements ] [ Send Feedback ]

Home • About Us •A-Z Index• Search •

1. Internationalized System Calls and Libraries Extended V3

Product Information

Environment Specification

Temporary Waivers

1.1 General Attributes

1.1.1 XSI Option Groups

1.1.2 Options

1.1.3 POSIX.1 Supported Features

1.1.4 Float, Stdio, and Limit Values

1.1.5 Error Conditions

1.1.6 Mathematical Interfaces

1.1.7 Data Encryption

1.2 Process Handling

1.2.1 Process Generation

1.3 File Handling

1.3.1 Access Control

1.3.2 Files and Directories

1.4 Internationalized System Interfaces

1.4.1 Coded Character Sets

1.5 Pseudo-Terminals

1.5.1 Master close

1.5.2 Slave close

1.5.3 Naming Conventions

1.6 Polling

1.7 Stack Growth Direction

1.8 Signal Codes

1.9 Set Process Group ID

1.10 Signals Generating a Core File

1.11 Sockets

1.11.1 Listen Queues

1.11.2 Address Families, Socket Types, and Protocols

1.11.3 Socket Types

1.12 Threads

1.12.1 Cancellation Points

1.13 C-language Compilation Environment

1.14 Realtime

1.14.1 Prioritized I/O

1.14.2 Cancelable Asynchronous I/O Operations

1.15 Realtime Threads

1.15.1 Scheduling Policies

1.15.2 Scheduling Contention Scope

1.15.3 Default Scheduling Contention Scope

2. Appendix

3. Change History