This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement Manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Internationalised System Calls and Libraries Extended V2

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternatively, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 General Attributes

1.1.1 Feature Groups

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

Response

Encryption	Yes   No
Legacy	Yes   No
Realtime	Yes   No
Realtime Threads	Yes   No

Support for a Feature Group can only be claimed if all interfaces in that group behave according to the relevant descriptions in System Interfaces and Headers, Issue 5.

The interfaces in these Groups must exist, whether or not the Feature Group is supported, and each interface must either behave according to the description in System Interfaces and Headers, Issue 5, or indicate an error, with errno set to [ENOSYS].

Rationale

System Interfaces and Headers, Issue 5 states that the system may provide one or more of the Feature Groups listed.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 1.2, Conformance and Section 1.3, Feature Groups.

Internationalised System Calls and Libraries Extended V2 Product Standard.

1.1.2 POSIX.1 Supported Features

Question 2: Which of the following options, specified in the <unistd.h> header file, are available on the system?

Response

Where indicated in the following table, select one of the options given (either "Yes" or "Variable"). Select "Variable" if there are system dependent or file_system dependent configuration procedures that can remove or modify any or all of these features.

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 Variable
_POSIX_NO_TRUNC	Pathname components longer than {NAME_MAX) generate an error.	Yes Variable
_POSIX_VDISABLE	Terminal special characters defined in <termios.h> can be disabled using this character value.	Yes Variable
_POSIX_SAVED_IDS	Each process has a saved set-user-ID and a saved set-group-ID.	Yes Variable
_POSIX_JOB_CONTROL	Implementation supports job control.	Yes Variable
_POSIX_THREADS	Implementation supports threads.	Yes Variable

If one of the above is Variable, describe in the area below the manner in which variations occur.

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <unistd.h>.

1.1.3 Float, Stdio and Limit Values

Question 3: 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.
FLT_MANT_DIG	Number of base-FLT_RADIX digits in the float significand.
DBL_MANT_DIG	Number of base-FLT_RADIX digits in the double significand.
LDBL_MANT_DIG	Number of base-FLT_RADIX digits in the long double significand.
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.
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.
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.
FLT_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised float.
DBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised double.
LDBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised long double.
FLT_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised floats.
DBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised doubles.
LDBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised long doubles.
FLT_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite float.
DBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite double.
LDBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite long double.
FLT_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite floats.
DBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite doubles.
LDBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite long doubles.
FLT_MAX	Maximum representable finite float.
DBL_MAX	Maximum representable finite double.
LDBL_MAX	Maximum representable finite long double.
FLT_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a float.
DBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a double.
LDBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a long double.
FLT_MIN	Minimum normalised positive float.
DBL_MIN	Minimum normalised positive double.
LDBL_MIN	Minimum normalised positive long double.

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <float.h>.

Question 4: 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.
AIO_LISTIO_MAX	Maximum number of I/O operations in a single list I/O call.
AIO_MAX	Maximum number of outstanding asynchronous I/O operations.
AIO_PRIO_DELTA_MAX	Maximum amount by which a process can decrease its asynchronous I/O priority level from its own scheduling level.
ATEXIT_MAX	Maximum number of functions that may be registered with atexit().
CHILD_MAX	Maximum number of processes per user ID.
DELAYTIMER_MAX	Maximum number of timer expiration overruns.
FILESIZEBITS	Minimum number of bits needed to represent as a signed integer value the maximum size of a regular file.
IOV_MAX	Maximum number of iovec structures that one process has available for use with readv() or writev().
LINK_MAX	Maximum number of links to a single file.
LOGIN_NAME_MAX	Maximum length of a login name.
MAX_CANON	Maximum number of bytes in a terminal canonical input line.
MAX_INPUT	Maximum number of bytes for which space will be available in a terminal input queue.
MQ_OPEN_MAX	Maximum number of open message queue descriptors a process may hold.
MQ_PRIO_MAX	Maximum number of message priorities supported by the implementation.
NAME_MAX	Maximum number of bytes in a filename (not including terminating null).
OPEN_MAX	Maximum number of open files that one process can have open at any one time.
PAGESIZE	Size of a page in bytes.
PAGE_SIZE	Same as PAGESIZE. If either PAGESIZE or PAGE_SIZE is defined, the other will be defined with the same value.
PASS_MAX	Maximum number of significant bytes in a password (not including the terminating null).
PATH_MAX	Maximum number of bytes in a pathname (including the terminating null).
PIPE_BUF	Maximum number of bytes that is guaranteed to be atomic when writing to a pipe.
PTHREAD_DESTRUCTOR_ITERATIONS	Maximum number of attempts made to destroy a thread's thread-specific data values on thread exit.
PTHREAD_KEYS_MAX	Maximum number of data keys that can be created by a process.
PTHREAD_STACK_MIN	Minimum size in bytes of thread stack storage.
PTHREAD_THREADS_MAX	Maximum number of threads that can be created by a process.
RTSIG_MAX	Maximum number of realtime signals reserved for application use.
SEM_NSEMS_MAX	Maximum number of semaphores that a process may have.
SEM_VALUE_MAX	Maximum value a semaphore may have.
SIGQUEUE_MAX	Maximum number of queued signals that a process may send and leave pending at the receiver(s) at any time.
STREAM_MAX	Number of streams that one process can have open at one time.
TIMER_MAX	Maximum number of timers per process supported.
TTY_NAME_MAX	Maximum length of terminal device name.
TZNAME_MAX	Maximum number of bytes supported for the name of a time zone.

Rationale

Each of these limits can vary within bounds set by System Interfaces and Headers, Issue 5. The minimum permitted value is specified in Chapter 4, <limits.h>.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <limits.h>.

Question 5: 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.
BC_DIM_MAX	Maximum number of elements permitted in an array by the bc utility.
BC_SCALE_MAX	Maximum scale value allowed by the bc utility.
BC_STRING_MAX	Maximum length of a string constant accepted by the bc utility.
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.
EXPR_NEST_MAX	Maximum number of expressions that can be nested within parentheses by the expr utility.
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.
NGROUPS_MAX	Maximum number of simultaneous supplementary group IDs per process.
RE_DUP_MAX	Maximum number of repeated occurrences of a regular expression permitted when using interval notation.

Rationale

Each of these limits can vary within bounds set by System Interfaces and Headers, Issue 5. 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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <limits.h>.

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

Response

Macro Name	Meaning	Value
CHAR_BIT	Number of bits in a char.
CHAR_MAX	Maximum value of a char.
INT_MAX	Maximum value of an int.
LONG_BIT	Number of bits in a long int.
LONG_MAX	Maximum value of a long int.
MB_LEN_MAX	Maximum number of bytes in a character, for any supported locale.
SCHAR_MAX	Maximum value of a signed char.
SHRT_MAX	Maximum value of a short.
SSIZE_MAX	Maximum value of an object of type ssize_t.
UCHAR_MAX	Maximum value of an unsigned char.
UINT_MAX	Maximum value of an unsigned int.
ULONG_MAX	Maximum value of an unsigned long int.
USHRT_MAX	Maximum value of an unsigned short int.
WORD_BIT	Number of bits in a word or int.

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <limits.h>.

Question 7: 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.
FOPEN_MAX	Number of streams which the implementation guarantees can be open simultaneously.
L_ctermid	Maximum size of character array to hold ctermid() output.
L_tmpnam	Maximum size of character array to hold tmpnam() output.
TMP_MAX	Minimum number of unique filenames generated by tmpnam(), which is the maximum number of times an application can call tmpnam() reliably.

Rationale

This set of constants provide useful information about the implementation.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <stdio.h>.

1.1.4 Error Conditions

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

Response

Function	Error	Detected
access()	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ETXTBSY	Yes   No
acos()	EDOM	Yes   No
acosh()	EDOM	Yes   No
aio_error()	EINVAL	Yes   No
asin()	EDOM	Yes   No
	ERANGE	Yes   No
asinh()	EDOM	Yes   No
atan()	EDOM	Yes   No
	ERANGE	Yes   No
atanh()	EDOM	Yes   No
atan2()	EDOM	Yes   No
	ERANGE	Yes   No
brk()	EAGAIN	Yes   No
	ENOMEM	Yes   No
catclose()	EBADF	Yes   No
	EINTR	Yes   No
catgets()	EBADF	Yes   No
	EINTR	Yes   No
	EINVAL	Yes   No
	ENOMSG	Yes   No
catopen()	EACCES	Yes   No
	EMFILE	Yes   No
	ENAMETOOLONG	Yes   No
	ENFILE	Yes   No
	ENOENT	Yes   No
	ENOMEM	Yes   No
	ENOTDIR	Yes   No
cbrt()	EDOM	Yes   No
ceil()	EDOM	Yes   No
cfsetispeed()	EINVAL	Yes   No
cfsetospeed()	EINVAL	Yes   No
chdir()	ENAMETOOLONG	Yes   No
chmod()	EINTR	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
chown()	EINTR	Yes   No
	EINVAL	Yes   No
	EIO	Yes   No
	ENAMETOOLONG	Yes   No
chroot()	ENAMETOOLONG	Yes   No
clock_settime()	EPERM	Yes   No
close()	EIO	Yes   No
closedir()	EBADF	Yes   No
	EINTR	Yes   No
cos()	EDOM	Yes   No
	ERANGE	Yes   No
cosh()	EDOM	Yes   No
endpwent()	EIO	Yes   No
erf()	EDOM	Yes   No
	ERANGE	Yes   No
erfc()	EDOM	Yes   No
	ERANGE	Yes   No
exec	ENAMETOOLONG	Yes   No
	ENOMEM	Yes   No
	ETXTBSY	Yes   No
exp()	EDOM	Yes   No
	ERANGE	Yes   No
expm1()	EDOM	Yes   No
	ERANGE	Yes   No
fabs()	EDOM	Yes   No
	ERANGE	Yes   No
fattach()	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	EXDEV	Yes   No
fchdir()	EINTR	Yes   No
	EIO	Yes   No
fchmod()	EINTR	Yes   No
	EINVAL	Yes   No
fchown()	EINVAL	Yes   No
	EIO	Yes   No
	EINTR	Yes   No
fclose()	ENXIO	Yes   No
fcntl()	EDEADLK	Yes   No
fdetach()	ENAMETOOLONG	Yes   No
fdopen()	EBADF	Yes   No
	EINVAL	Yes   No
	EMFILE	Yes   No
	ENOMEM	Yes   No
fflush()	ENXIO	Yes   No
fgetc()	ENOMEM	Yes   No
	ENXIO	Yes   No
fgetpos()	EBADF	Yes   No
	ESPIPE	Yes   No
fgetwc()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
fileno()	EBADF	Yes   No
floor()	EDOM	Yes   No
fmod()	EDOM	Yes   No
	ERANGE	Yes   No
fopen()	EINVAL	Yes   No
	EMFILE	Yes   No
	ENAMETOOLONG	Yes   No
	ENOMEN	Yes   No
	ETXTBSY	Yes   No
fork()	ENOMEM	Yes   No
fpathconf()	EBADF	Yes   No
	EINVAL	Yes   No
fprintf()	EINVAL	Yes   No
	EILSEQ	Yes   No
	ENOMEM	Yes   No
fputc()	ENOMEM	Yes   No
	ENXIO	Yes   No
fputwc()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
fread()	ENOMEM	Yes   No
	ENXIO	Yes   No
freopen()	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENOMEM	Yes   No
	ENXIO	Yes   No
	ETXTBSY	Yes   No
frexp()	EDOM	Yes   No
fscanf()	EILSEQ	Yes   No
	EINVAL	Yes   No
	ENOMEM	Yes   No
	ENXIO	Yes   No
fsetpos()	EBADF	Yes   No
	ESPIPE	Yes   No
fstat()	EOVERFLOW	Yes   No
ftok()	ENAMETOOLONG	Yes   No
ftw()	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
fwide()	EBADF	Yes   No
fwprintf()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
	EINVAL	Yes   No
fwscanf()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
	EINVAL	Yes   No
getcwd()	EACCES	Yes   No
	ENOMEM	Yes   No
getgrent()	EINTR	Yes   No
	EIO	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getgrgid()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getgrgid_r()	ERANGE	Yes   No
getgrnam()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getgrnam_r()	ERANGE	Yes   No
getitimer()	EINVAL	Yes   No
getlogin()	EMFILE	Yes   No
	ENFILE	Yes   No
	ENXIO	Yes   No
getlogin_r()	ERANGE	Yes   No
getpass()	EINTR	Yes   No
	EIO	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
	ENXIO	Yes   No
getpgid()	EINVAL	Yes   No
getpwent()	EIO	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getpwnam()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getpwnam_r()	ERANGE	Yes   No
getpwuid()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getpwuid_r()	ERANGE	Yes   No
grantpt()	EBADF	Yes   No
	EINVAL	Yes   No
	EACCES	Yes   No
hcreate()	ENOMEM	Yes   No
hsearch()	ENOMEM	Yes   No
hypot()	EDOM	Yes   No
	ERANGE	Yes   No
iconv()	EBADF	Yes   No
iconv_close()	EBADF	Yes   No
iconv_open()	EMFILE	Yes   No
	ENFILE	Yes   No
	ENOMEM	Yes   No
	EINVAL	Yes   No
isatty()	EBADF	Yes   No
	ENOTTY	Yes   No
j0()	EDOM	Yes   No
	ERANGE	Yes   No
j1()	EDOM	Yes   No
	ERANGE	Yes   No
jn()	EDOM	Yes   No
	ERANGE	Yes   No
lchown()	EIO	Yes   No
	EINTR	Yes   No
	ENAMETOOLONG	Yes   No
ldexp()	EDOM	Yes   No
	ERANGE	Yes   No
lgamma()	EDOM	Yes   No
	ERANGE	Yes   No
link()	ENAMETOOLONG	Yes   No
lockf()	EAGAIN	Yes   No
	EDEADLK	Yes   No
	EINVAL	Yes   No
	ENOLCK	Yes   No
	EOPNOTSUPP	Yes   No
log()	EDOM	Yes   No
	ERANGE	Yes   No
log10()	EDOM	Yes   No
	ERANGE	Yes   No
log1p()	EDOM	Yes   No
	ERANGE	Yes   No
logb()	EDOM	Yes   No
lstat()	ENAMETOOLONG	Yes   No
	EOVERFLOW	Yes   No
mblen()	EILSEQ	Yes   No
mbrlen()	EINVAL	Yes   No
	EILSEQ	Yes   No
mbrtowc()	EINVAL	Yes   No
	EILSEQ	Yes   No
mbsrtowcs()	EINVAL	Yes   No
mbstowcs()	EILSEQ	Yes   No
mbtowc()	EILSEQ	Yes   No
mkdir()	ENAMETOOLONG	Yes   No
mkfifo()	ENAMETOOLONG	Yes   No
mknod()	ENAMETOOLONG	Yes   No
mlock()	EINVAL	Yes   No
	ENOMEM	Yes   No
	EPERM	Yes   No
mlockall()	ENOMEM	Yes   No
	EPERM	Yes   No
modf()	EDOM	Yes   No
	ERANGE	Yes   No
mq_receive()	EBADMSG	Yes   No
munlock()	EINVAL	Yes   No
nextafter()	EDOM	Yes   No
nftw()	ELOOP	Yes   No
	EMFILE	Yes   No
	ENAMETOOLONG	Yes   No
	ENFILE	Yes   No
open()	EAGAIN	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENOMEM	Yes   No
	ETXTBSY	Yes   No
opendir()	EMFILE	Yes   No
	ENAMETOOLONG	Yes   No
	ENFILE	Yes   No
pathconf()	EACCES	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENOENT	Yes   No
	ENOTDIR	Yes   No
popen()	EMFILE	Yes   No
	EINVAL	Yes   No
pow()	EDOM	Yes   No
	ERANGE	Yes   No
pread()	ENXIO	Yes   No
printf()	ENOMEM	Yes   No
pthread_attr_setinheritsched()	EINVAL	Yes   No
	ENOTSUP	Yes   No
pthread_attr_setschedparam()	EINVAL	Yes   No
	ENOTSUP	Yes   No
pthread_attr_setschedpolicy()	EINVAL	Yes   No
	ENOTSUP	Yes   No
pthread_attr_setscope()	EINVAL	Yes   No
	ENOTSUP	Yes   No
pthread_cancel()	ESRCH	Yes   No
pthread_cond_init()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_cond_destroy()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_cond_broadcast()	EINVAL	Yes   No
pthread_cond_signal()	EINVAL	Yes   No
pthread_cond_timedwait()	EINVAL	Yes   No
pthread_cond_wait()	EINVAL	Yes   No
pthread_condattr_destroy()	EINVAL	Yes   No
pthread_condattr_setpshared()	EINVAL	Yes   No
pthread_getschedparam()	ESRCH	Yes   No
pthread_join()	EDEADLK	Yes   No
pthread_key_delete()	EINVAL	Yes   No
pthread_mutex_destroy()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_mutex_getprioceiling()	EINVAL	Yes   No
	ENOSYS	Yes   No
	EPERM	Yes   No
pthread_mutex_init()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_mutex_lock()	EINVAL	Yes   No
	EAGAIN	Yes   No
	EDEADLK	Yes   No
pthread_mutex_trylock()	EINVAL	Yes   No
	EAGAIN	Yes   No
pthread_mutex_unlock()	EINVAL	Yes   No
	EAGAIN	Yes   No
	EPERM	Yes   No
pthread_mutex_setprioceiling()	EINVAL	Yes   No
	ENOSYS	Yes   No
	EPERM	Yes   No
pthread_mutexattr_destroy()	EINVAL	Yes   No
pthread_mutexattr_getprioceiling()	EINVAL	Yes   No
	EPERM	Yes   No
pthread_mutexattr_getprotocol()	EINVAL	Yes   No
	EPERM	Yes   No
pthread_mutexattr_gettype()	EINVAL	Yes   No
pthread_mutexattr_init()	ENOMEM	Yes   No
pthread_mutexattr_setprioceiling()	EINVAL	Yes   No
	EPERM	Yes   No
pthread_mutexattr_setprotocol()	EINVAL	Yes   No
	EPERM	Yes   No
pthread_mutexattr_setpshared()	EINVAL	Yes   No
pthread_mutexattr_settype()	EINVAL	Yes   No
pthread_rwlock_destroy()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_rwlock_init()	EBUSY	Yes   No
	EINVAL	Yes   No
pthread_rwlock_rdlock()	EINVAL	Yes   No
	EDEADLCK	Yes   No
	EAGAIN	Yes   No
pthread_rwlock_tryrdlock()	EINVAL	Yes   No
	EDEADLCK	Yes   No
	EAGAIN	Yes   No
pthread_rwlock_trywrlock()	EINVAL	Yes   No
	EDEADLCK	Yes   No
pthread_rwlock_unlock()	EINVAL	Yes   No
	EPERM	Yes   No
pthread_rwlock_wrlock()	EINVAL	Yes   No
	EDEADLCK	Yes   No
pthread_rwlockattr_destroy()	EINVAL	Yes   No
pthread_rwlockattr_setpshared()	EINVAL	Yes   No
pthread_setcanceltype()	EINVAL	Yes   No
pthread_setschedparam()	EINVAL	Yes   No
	ENOTSUP	Yes   No
	EPERM	Yes   No
pthread_setspecific()	EINVAL	Yes   No
putc()	ENOMEM	Yes   No
	ENXIO	Yes   No
putchar()	ENOMEM	Yes   No
	ENXIO	Yes   No
putenv()	ENOMEM	Yes   No
puts()	ENOMEM	Yes   No
	ENXIO	Yes   No
pututxline()	EPERM	Yes   No
putw()	ENOMEM	Yes   No
	ENXIO	Yes   No
putwc()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
putwchar()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
pwrite()	EINVAL	Yes   No
	ENXIO	Yes   No
read()	ENXIO	Yes   No
readdir()	EBADF	Yes   No
	ENOENT	Yes   No
readdir_r()	EBADF	Yes   No
readlink()	EACCES	Yes   No
	ENAMETOOLONG	Yes   No
readv()	EINVAL	Yes   No
	ENXIO	Yes   No
realpath()	ENAMETOOLONG	Yes   No
	ENOMEM	Yes   No
regcmp()	ENOMEM	Yes   No
remainder()	EDOM	Yes   No
remove()	EBUSY	Yes   No
	ENAMETOOLONG	Yes   No
	ETXTBSY	Yes   No
rename()	EBUSY	Yes   No
	ENAMETOOLONG	Yes   No
	ETXTBSY	Yes   No
rint()	EDOM	Yes   No
rmdir()	ENAMETOOLONG	Yes   No
sbrk()	EAGAIN	Yes   No
	ENOMEM	Yes   No
scalb()	EDOM	Yes   No
sem_destroy()	EBUSY	Yes   No
sem_trywait()	EDEADLCK	Yes   No
	EINTR	Yes   No
sem_wait()	EDEADLCK	Yes   No
	EINTR	Yes   No
setitimer()	EINVAL	Yes   No
setpriority()	EPERM	Yes   No
	EACCES	Yes   No
setpwent()	EIO	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
setrlimit()	EINVAL	Yes   No
setvbuf()	EBADF	Yes   No
shmctl()	EOVERFLOW	Yes   No
sigaction()	EINVAL	Yes   No
sigaddset()	EINVAL	Yes   No
sigdelset()	EINVAL	Yes   No
sigismember()	EINVAL	Yes   No
signal()	EINVAL	Yes   No
sigtimedwait()	EINVAL	Yes   No
	EINTR	Yes   No
sigwait()	EINVAL	Yes   No
sigwaitinfo()	EINTR	Yes   No
sin()	EDOM	Yes   No
	ERANGE	Yes   No
sinh()	EDOM	Yes   No
	ERANGE	Yes   No
sqrt()	EDOM	Yes   No
stat()	ENAMETOOLONG	Yes   No
	EOVERFLOW	Yes   No
statvfs()	ENAMETOOLONG	Yes   No
strcoll()	EINVAL	Yes   No
strdup()	ENOMEM	Yes   No
strerror()	EINVAL	Yes   No
strtod()	EINVAL	Yes   No
strtol()	EINVAL	Yes   No
strtoul()	EINVAL	Yes   No
strxfrm()	EINVAL	Yes   No
swprintf()	EILSEQ	Yes   No
	EINVAL	Yes   No
swcsanf()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
symlink()	ENAMETOOLONG	Yes   No
system()	ECHILD	Yes   No
tan()	EDOM	Yes   No
	ERANGE	Yes   No
tanh()	EDOM	Yes   No
	ERANGE	Yes   No
tcdrain()	EIO	Yes   No
tcflow()	EIO	Yes   No
tcflush()	EIO	Yes   No
tcsendbreak()	EIO	Yes   No
tcsetattr()	EIO	Yes   No
tmpfile()	EMFILE	Yes   No
	ENOMEM	Yes   No
towctrans()	EINVAL	Yes   No
truncate()	ENAMETOOLONG	Yes   No
ttyname()	EBADF	Yes   No
	ENOTTY	Yes   No
ttyname_r()	EBADF	Yes   No
	ENOTTY	Yes   No
	ERANGE	Yes   No
ungetwc()	EILSEQ	Yes   No
unlink()	EBUSY	Yes   No
	ENAMETOOLONG	Yes   No
	ETXTBSY	Yes   No
unlockpt()	EBADF	Yes   No
	EINVAL	Yes   No
usleep()	EINVAL	Yes   No
utime()	ENAMETOOLONG	Yes   No
utimes()	ENAMETOOLONG	Yes   No
wait3()	ECHILD	Yes   No
wcrtomb()	EINVAL	Yes   No
	EILSEQ	Yes   No
wcsrtombs()	EINVAL	Yes   No
	EILSEQ	Yes   No
wcscoll()	EINVAL	Yes   No
wcstod()	EINVAL	Yes   No
wcstol()	EINVAL	Yes   No
wcstombs()	EILSEQ	Yes   No
wcstoul()	EINVAL	Yes   No
wcsxfrm()	EINVAL	Yes   No
wctrans()	EINVAL	Yes   No
wprintf()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
	EINVAL	Yes   No
write()	EINVAL	Yes   No
	ENXIO	Yes   No
writev()	EINVAL	Yes   No
	ENXIO	Yes   No
wscanf()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
y0()	EDOM	Yes   No
	ERANGE	Yes   No
y1()	EDOM	Yes   No
	ERANGE	Yes   No
yn()	EDOM	Yes   No
	ERANGE	Yes   No

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.3, Error Numbers.

1.1.5 Mathematical Interfaces

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

Response

Either use the default answer or provide a description of the floating point format used by your implementation.

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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 1.6, Relationship to Formal Standards.

1.1.6 Data Encryption

Question 10: Are the optional data encryption interfaces provided?

Response

Mark each of the following table entries appropriately. If your implementation is effected by any export restrictions imposed by the US Government, indicate these restrictions in the following area.

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

Export Restrictions:

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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 1.2, Conformance.

1.2 Process Handling

1.2.1 Process Generation

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

Response

Enter the file types that are executable on your implementation in the area below.

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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, exec.

1.3 File Handling

1.3.1 Access Control

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

Response

Either indicate that "Standard access control is provided.", that the reader should "Refer to the POSIX.1 Conformance Document, Section 2.4", or provide a detailed description of the access control and/or additional or alternate access mechanisms on your implementation.

Rationale

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

Reference

CAE Specification, System Interface Definitions, Issue 5, Chapter 2, Glossary, file access permissions.

1.3.2 Files and Directories

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

Response

Yes   No

Rationale

System Interfaces and Headers, Issue 5 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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, fstat() and stat().

1.3.3 Formatting Interfaces

Question 14: Does the printf() function produce character string representations for Infinity and NaN to represent the respective values?

Response

Yes   No

Rationale

This behaviour is often provided on systems with mathematical functions that produce these results.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, fprintf().

1.4 Internationalised System Interfaces

1.4.1 Coded Character Sets

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

Response

Rationale

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

Reference

CAE Specification, System Interface Definitions, Issue 5, Chapter 4, Character Set.

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

Response

If the implementation does not use ISO 8859-1:1987, provide the name or description of the underlying codeset.

Rationale

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

Reference

CAE Specification, System Interface Definitions, Issue 5, Chapter 4, Character Set.

1.5 STREAMS

Question 17: What networking services or other character-based I/O device types are implemented using STREAMS in addition to pseudo-terminals?

Response

Enter the device types that are streams-based on this implementation. If your implementation does not support streams, state None.

Rationale

System Interfaces and Headers, Issue 5, defines that STREAMS provide a uniform mechanism for implementing networking services and other character-based I/O. However, the specification does not mandate which device or file types should be STREAMS-based, except for requiring that STREAMS-based pseudo-terminals be provided. Although applications are discouraged from making assumptions in this area, it may be that certain applications are sensitive to whether interfaces such as getmsg() and putmsg(), for example, are supported on specific device or file types.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.5, STREAMS.

1.6 Pseudo-Terminals

1.6.1 Master close

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

Response

Yes   No

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, close().

1.6.2 Slave close

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

Response

Yes   No

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, close().

1.6.3 Naming Conventions

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

Response

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, open().

1.7 Polling

Question 21: What types of file can be polled?

Response

Update the following list with any additional implementation-specific file types that can be polled.

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.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, poll().

1.8 Stack Growth Direction

Question 22: What is the direction of stack growth?

From lower to higher addresses. From higher to lower addresses. See the Appendix in Section 2 for Details

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 3, System Interfaces, sigstack(). Conformance requires that an implementation supports alternate signal stacks. The APPLICATION USAGE section of the sigaltstack() entry describes one method using malloc() to perform this function. However, the specification does not guarantee that malloc'ed space can be used in this way, nor does it define a specific alternate stack allocation routine.

1.9 Signal Codes

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

Response

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

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <signal.h>.

1.10 Set Process Group ID

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

Response

Yes   No

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, setpgrp().

1.11 Signals Generating a Core File

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

Response

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

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <signal.h>.

1.12 Realtime

1.12.1 Prioritized I/O

Question 26: Does the implementation support _POSIX_PRIORITIZED_IO?

Response

The system does not support _POSIX_PRIORITIZED_IO.

The system supports _POSIX_PRIORITIZED_IO for the following file types:

Rationale

Support for _POSIX_PRIORITIZED_IO is optional.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 1.3,2, Realtime.

1.12.2 Cancelable Asynchronous I/O Operations

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

Response

If the Realtime feature group is supported, list the operation that are changeable in the text area below, otherwise type not applicable

Rationale

The operations which are cancelable are implementation-dependent.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 3, System Interfaces, aio_cancel().

1.13 Threads

1.13.1 Cancellation Points

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

Response

There are many functions which may have a cancellation point listed in XSH, Section 2.8.8.2. Select those which have cancellation points in your implementation.

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

Rationale

System Interface Definitions, Issue 5 states that a cancellation point may occur for these functions.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.8.8.2, Cancellation Points.

1.14 Realtime Threads

1.14.1 Scheduling Policies

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

Response

If the Realtime Threads feature group is supported, describe the scheduling policy provided by the implementation when SCHED_OTHER is requested. If this policy executes identically with SCHED_FIFO or SCHED_RR, this should be indicated. Otherwise a complete description must be provided, including the scheduling parameters used with pthread_getschedparam and pthread_setschedparam. Otherwise, type not applicable.

Rationale

System Interface Definitions, Issue 5 states that conforming implementations must support a scheduling policy identified as SCHED_OTHER but defines its effects as implementation-dependent.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.7.4, Scheduling Policies.

1.14.2 Scheduling Contention Scope

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

Response

Not applicable - the Realtime Threads feature group is not supported.
PTHREAD_SCOPE_PROCESS.
PTHREAD_SCOPE_SYSTEM.
Both PTHREAD_SCOPE_PROCESS and PTHREAD_SCOPE_SYSTEM.

Rationale

System Interface Definitions, Issue 5 states that conforming implementations will support PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.8.3, Thread Scheduling Contention Scope.

1.14.3 Default Scheduling Contention Scope

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

Response

Not applicable - the Realtime Treads feature group is not supported.
PTHREAD_SCOPE_PROCESS.
PTHREAD_SCOPE_SYSTEM.

Rationale

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

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Section 2.8.2, Thread Scheduling Attributes.

1.15 C-language Compilation Environment

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

Response

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

Rationale

System Interfaces and Headers, Issue 5 defines these scenarios as possible C-language compilation environment offerings.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <unistd.h>.

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   No
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   No
The implementation provides an execution environment with 32-bit int, and 64-bit long, pointer and off_t types.	Yes   No
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   No

Rationale

System Interfaces and Headers, Issue 5 defines four scenarios as possible C-language compilation environment offerings but does not define which corresponding execution environments are supported.

Reference

CAE Specification, System Interfaces and Headers, Issue 5, Chapter 4, Headers, <unistd.h>.

2. Appendix

Copyright © 
All rights reserved.

3. Change History