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. Multi-Purpose Realtime Operating System

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, 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 Supported Options

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

Response

Threads Option	Yes   No
Realtime Threads Feature Group	Yes   No

For a conforming implementation, these features are optional, with the following dependency:

If the Realtime Threads Feature Group is supported then the Threads option shall be supported.

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, Chapter 4, Headers, <unistd.h>

Multi-Purpose Realtime Operating System Product Standard.

1.2 General Attributes

1.2.1 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_ASYNCHRONOUS_IO	Implementation supports the Asynchronous Input and Output option.	Yes No
_POSIX_FSYNC	Implementation supports the File Synchronisation option.	Yes No
_POSIX_MEMLOCK	Implementation supports the Process Memory Locking option.	Yes No
_POSIX_MEMLOCK_RANGE	Implementation supports the Range Memory Locking option.	Yes No
_POSIX_MAPPED_FILES	Implementation supports the Memory Mapped Files option.	Yes No
_POSIX_MEMORY_PROTECTION	Implementation supports the Memory Protection option.	Yes No
_POSIX_MESSAGE_PASSING	Implementation supports the Message Passing option.	Yes No
_POSIX_PRIORITY_SCHEDULING	Implementation supports the Process Scheduling option.	Yes No
_POSIX_REALTIME_SIGNALS	Implementation supports the Realtime Signals option.	Yes No
_POSIX_SEMAPHORES	Implementation supports the Semaphores option.	Yes No
_POSIX_SHARED_MEMORY_OBJECTS	Implementation supports the Shared Memory Objects option.	Yes No
_POSIX_SYNCHRONIZED_IO	Implementation supports the Synchronized Input and Output option.	Yes No
_POSIX_TIMERS	Implementation supports the Timers option.	Yes No

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

Multi-Purpose Realtime Operating System Product Standard.

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

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 6: 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.2.3 Error Conditions

Question 7: 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
aio_error()	EINVAL	Yes   No
asin()	ERANGE	Yes   No
atan()	ERANGE	Yes   No
atan2()	ERANGE	Yes   No
chown()	EINVAL	Yes   No
clock_settime()	EPERM	Yes   No
closedir()	EBADF	Yes   No
cos()	ERANGE	Yes   No
exec	ENOMEM	Yes   No
exp()	ERANGE	Yes   No
fabs()	ERANGE	Yes   No
fcntl()	EDEADLK	Yes   No
fmod()	ERANGE	Yes   No
fopen()	ENOMEN	Yes   No
fork()	ENOMEM	Yes   No
fpathconf()	EBADF	Yes   No
	EINVAL	Yes   No
fscanf()
	ENOMEM	Yes   No
	ENXIO	Yes   No
getcwd()	EACCES	Yes   No
getgrgid_r()	ERANGE	Yes   No
getgrnam_r()	ERANGE	Yes   No
getlogin_r()	ERANGE	Yes   No
getpwnam_r()	ERANGE	Yes   No
getpwuid_r()	ERANGE	Yes   No
ldexp()	ERANGE	Yes   No
log()	ERANGE	Yes   No
log10()	ERANGE	Yes   No
mlock()	EINVAL	Yes   No
	ENOMEM	Yes   No
mlockall()	ENOMEM	Yes   No
	EPERM	Yes   No
modf()	ERANGE	Yes   No
mq_receive()	EBADMSG	Yes   No
munlock()	EINVAL	Yes   No
opendir()	EMFILE	Yes   No
	ENFILE	Yes   No
pathconf()	EACCES	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENOENT	Yes   No
	ENOTDIR	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_setschedscope()	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_setcanceltype()	EINVAL	Yes   No
pthread_setschedparam()	EINVAL	Yes   No
	ENOTSUP	Yes   No
	EPERM	Yes   No
pthread_setspecific()	EINVAL	Yes   No
readdir()	EBADF	Yes   No
readdir_r()	EBADF	Yes   No
sem_destroy()	EBUSY	Yes   No
sem_trywait()	EDEADLCK	Yes   No
	EINTR	Yes   No
sem_wait()	EDEADLCK	Yes   No
	EINTR	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()	ERANGE	Yes   No
sinh()	ERANGE	Yes   No
tan()	ERANGE	Yes   No
tanh()	ERANGE	Yes   No
tmpfile()	ENOMEM	Yes   No
ttyname_r()	EBADF	Yes   No
	ENOTTY	Yes   No
	ERANGE	Yes   No
wcstombs()	EILSEQ	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.3 Process Handling

1.3.1 Process Generation

Question 8: 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.4 File Handling

1.4.1 Access Control

Question 9: 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.4.2 Files and Directories

Question 10: 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.5 Realtime

1.5.1 Prioritized I/O

Question 11: 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.5.2 Cancelable Asynchronous I/O Operations

Question 12: What asynchronous I/O operations are cancelable with aio_cancel()?

Response

List the operation that are changeable in the text area below

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.6 Threads

1.6.1 POSIX.1 Supported Features

Question 13: 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 "No").

Macro Name	Meaning	Provided
_POSIX_THREADS	Implementation supports threads.	Yes No
_POSIX_THREAD_SAFE_FUNCTIONS	Implementation supports the thread-safe functions option.	Yes No
_POSIX_THREAD_ATTR_STACKADDR	Implementation supports the thread stack address attribute.	Yes No
_POSIX_THREAD_ATTR_STACKSIZE	Implementation supports the thread stack size attribute.	Yes No
_POSIX_THREAD_PROCESS_SHARED	Implementation supports the process-shared synchronization option.	Yes No

Rationale

For a conforming implementation, if the Threads option is supported then all of these POSIX features must be provided.

Reference

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

Multi-Purpose Realtime Operating System Product Standard.

1.6.2 Cancellation Points

Question 14: 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. List those which have cancellation points in the base below:

Rationale

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

Reference

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

1.7 Realtime Threads

1.7.1 Scheduling Policies

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

Response

Not applicable - the Realtime Threads feature group is not supported.

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.

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.7.2 Scheduling Contention Scope

Question 16: 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.7.3 Default Scheduling Contention Scope

Question 17: 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.

2. Appendix

Copyright © 
All rights reserved.

3. Change History