|
|
Product Standard: PSE52 Realtime Controller 1003.13-2003 System
[Note to submitter: This form contains a series of questions that need to be answered. Please complete all the fields in the questionnaire below to produce a conformance statement for your product. This should be submitted as part of product registration within the web certification system. See the Guide to POSIX Certification for more information. Please note that this conformance statement will appear on the public register of certified products.]
Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.
| Organization | Enter_Organization_Name |
|---|---|
| Author | Enter_Author_Name |
Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements. If more than one product is required, please list the additional products, and extend the table if necessary.
| Product Identification | Version/Release Number | Product Supplier |
|---|---|---|
| Enter_Product_Identification | Enter_Version_or_Release_Number | Enter_Product_Supplier_Name |
Product registration applies to software products operating in a specific hardware or hardware/software
environment.
A product may be registered either as a single product, known as Platform Specific Certification, or as a family of
binary-compatible products, known as Product Family Certification.
Enter the level of Certification, either "Platform Specific Certification" or "Product Family Certification". If Product Family Certification then enter a full description below of the binary-compatible family
| Level of Certification | Binary-compatible Family |
|---|---|
| Enter_Certification_Level |
Enter the precise hardware/software environment(s) tested and test suite and version number. If Product Family Certification then two testing environments should be entered below.
| Testing Environment | Indicator of Compliance Details |
|---|---|
| Enter_Testing_Environment
|
Test Suite Name:
Enter_Test_Suite_Name Test Suite Version: Enter_Test Suite_Version |
Question PCD-1: How can a copy of the POSIX Conformance Document for this product be obtained?
Response
Provide a description of how the POSIX Conformance Document for this product can be obtained.
Rationale
Implementations claiming conformance to IEEE Std 1003.13-2003 are required to create a conformance document or to cite a reference to an existing conformance document for IEEE Std 1003.1.
Reference
IEEE Std 1003.1, 2003 Edition, Base Definitions Volume, Issue 6, Section 2.1 Implementation Conformance, Section 2.1.2 Documentation.
IEEE Std 1003.13-2003, Section 5: Conformance.
Question SI-1: Are the required features below supported for all system configurations?
Response
Where indicated in the following table, enter one of the options given (either "Yes" or "Variable"). Enter "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_NO_TRUNC Pathname components longer than {NAME_MAX) generate an error. Enter_Yes_or_Variable
If the above is Variable, describe in the area below the manner in which variations occur.
Rationale
Although all implementations conforming to IEEE Std 1003.1-2001 support the features described above, there may be system-dependent or file system-dependent configuration procedures that can remove or modify any or all of these features. Such configurations should not be made if strict compliance is required.
Reference
IEEE Std 1003.1, 2003 Edition, Section 2.1.3, POSIX Conformance.
Question SI-2: Which options from the PSE52-2003 Product Standard does this implementation claim support for?
Response
Where indicated in the following table, for the options given answer either "Yes" or "No".
Option Provided _POSIX_TRACE Enter_Yes_or_No _POSIX_TRACE_EVENT_LOG Enter_Yes_or_No _POSIX_TRACE_LOG Enter_Yes_or_No POSIX 1003.26-2003 Enter_Yes_or_No POSIX.5c Interfaces (Ada Language Option) Enter_Yes_or_No
Rationale
These features are optional in the PSE52 Realtime Controller 1003.13TM-2003 System Product Standard.
Reference
PSE52 Realtime Controller 1003.13TM-2003 System Product Standard
Question SI-3: Which POSIX.1 options and POSIX.13 units of functionality not mandated by this product standard does the system claim support for?
Response
Provide a list of the POSIX.1 options and POSIX.13 units of functionality supported by the implementation that are not required by this product standard. Examples are values from <unistd.h> such as _POSIX_ADVISORY_INFO and units of functionality from 1003.13 section 1.4, for example POSIX_NETWORKING
Rationale
It is optional whether an implementation claims support for the features associated with these options. This is useful information for procurers and application writers.
Reference
PSE52 Realtime Controller 1003.13-2003 System Product Standard.
Question SI-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. Enter_a_value FLT_MANT_DIG Number of base-FLT_RADIX digits in the float significand. Enter_a_value DBL_MANT_DIG Number of base-FLT_RADIX digits in the double significand. Enter_a_value LDBL_MANT_DIG Number of base-FLT_RADIX digits in the long double significand. Enter_a_value 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. Enter_a_value 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. Enter_a_value 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. Enter_a_value FLT_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised float. Enter_a_value DBL_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised double. Enter_a_value LDBL_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised long double. Enter_a_value FLT_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised floats. Enter_a_value DBL_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised doubles. Enter_a_value LDBL_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised long doubles. Enter_a_value FLT_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite float. Enter_a_value DBL_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite double. Enter_a_value LDBL_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite long double. Enter_a_value FLT_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite floats. Enter_a_value DBL_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite doubles. Enter_a_value LDBL_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite long doubles. Enter_a_value FLT_MAX Maximum representable finite float. Enter_a_value DBL_MAX Maximum representable finite double. Enter_a_value LDBL_MAX Maximum representable finite long double. Enter_a_value FLT_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a float. Enter_a_value DBL_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a double. Enter_a_value LDBL_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a long double. Enter_a_value FLT_MIN Minimum normalised positive float. Enter_a_value DBL_MIN Minimum normalised positive double. Enter_a_value LDBL_MIN Minimum normalised positive long double. Enter_a_value
Rationale
This set of constants provides useful information regarding the underlying architecture of the implementation.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <float.h>.
Question SI-5: What are the values associated with the following constants (optionally specified in the <limits.h> header file)?
Response
For the lines in the table below, add the minimum and maximum values for your implementation. This value 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() or pathconf(), or as defined in <limits.h>. The maximum value should be the largest value that is returned from sysconf() or pathconf().
Macro Name Meaning Minimum Maximum DELAYTIMER_MAX Maximum number of timer expiration overruns. Enter_minimum Enter_maximum FILESIZEBITS Minimum number of bits needed to represent as a signed integer value the maximum size of a regular file. Enter_minimum Enter_maximum LINK_MAX Maximum number of links to a single file. Enter_minimum Enter_maximum MQ_OPEN_MAX The maximum number of open message queue descriptors a process may hold. Enter_minimum Enter_maximum MQ_PRIO_MAX The maximum number of message priorities supported by the implementation. Enter_minimum Enter_maximum NAME_MAX Maximum number of bytes in a filename (not including terminating null). Enter_minimum Enter_maximum OPEN_MAX Maximum number of open files that one process can have open at any one time. Enter_minimum Enter_maximum PAGESIZE Size of a page in bytes. Enter_minimum Enter_maximum PATH_MAX Maximum number of bytes in a pathname (including the terminating null). Enter_minimum Enter_maximum PTHREAD_DESTRUCTOR_ITERATIONS Maximum number of attempts made to destroy a thread's thread-specific data values on thread exit. Enter_minimum Enter_maximum PTHREAD_KEYS_MAX Maximum number of data keys that can be created by a process. Enter_minimum Enter_maximum PTHREAD_STACK_MIN Minimum size in bytes of thread stack storage. Enter_minimum Enter_maximum PTHREAD_THREADS_MAX Maximum number of threads that can be created per process. Enter_minimum Enter_maximum RTSIG_MAX Maximum number of realtime signals reserved for application use in this implementation. Enter_minimum Enter_maximum SEM_NSEMS_MAX Maximum number of semaphores that a process may have. Enter_minimum Enter_maximum SEM_VALUE_MAX The maximum value a semaphore may have. Enter_minimum Enter_maximum SIGQUEUE_MAX Maximum number of queued signals that a process may send and have pending at the receiver(s) at any time. Enter_minimum Enter_maximum SS_REPL_MAX The maximum number of replenishment operations that may be simultaneously pending for a particular sporadic server scheduler. Enter_minimum Enter_maximum STREAM_MAX Number of streams that one process can have open at one time. Enter_minimum Enter_maximum TIMER_MAX Maximum number of timers per process supported by the implementation. Enter_minimum Enter_maximum TRACE_EVENT_NAME_MAX Maximum length of the trace event name. Enter_minimum Enter_maximum TRACE_NAME_MAX Maximum length of the trace generation version string or of the trace stream name. Enter_minimum Enter_maximum TRACE_SYS_MAX Maximum number of trace streams that may simultaneously exist in the system. Enter_minimum Enter_maximum TRACE_USER_EVENT_MAX Maximum number of user trace event type identifiers that may simultaneously exist in a traced process, including the predefined user trace event POSIX_TRACE_UNNAMED_USER_EVENT. Enter_minimum Enter_maximum TZNAME_MAX Maximum number of bytes supported for the name of a time zone. Enter_minimum Enter_maximum
Rationale
Each of these limits can vary within bounds set by the Base Definitions Volume. Except as noted below the minimum permitted value is specified in Chapter 13, <limits.h>.
IEEE Std 1003.13-2003 Chapter 7 states that the value of TIMER_MAX shall be at least 64, and the value of RTSIG_MAX shall be at least 16.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <limits.h>.
IEEE Std 1003.13, 2003 Edition, Section 7, Realtime Controller System Profile (PSE52).
Question SI-6: 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. Enter_value INT_MAX Maximum value of an int. Enter_value LONG_MAX Maximum value of a long int. Enter_value LLONG_MAX Maximum value of a long long. Enter_value SHRT_MAX Maximum value of a short. Enter_value SSIZE_MAX Maximum value of an object of type ssize_t. Enter_value UINT_MAX Maximum value of an unsigned int. Enter_value ULONG_MAX Maximum value of an unsigned long int. Enter_value ULLONG_MAX Maximum value of a unigsned long long. Enter_value USHRT_MAX Maximum value of an unsigned short int. Enter_value
Rationale
This set of constants provides useful information regarding the underlying architecture of the implementation.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <limits.h>.
Question SI-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. Enter_value FOPEN_MAX Number of streams which the implementation guarantees can be open simultaneously. Enter_value L_tmpnam Maximum size of character array to hold tmpnam() output. Enter_value TMP_MAX Minimum number of unique filenames generated by tmpnam(), which is the maximum number of times an application can call tmpnam() reliably. Enter_value
Rationale
This set of constants provides useful information about the implementation.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <stdio.h>.
Question SI-8: Which of the following option errors, ( denoted by "may fail" within the specification ), listed in the System Interfaces Volume are detected in the circumstances specified?
Response
Enter Yes or No. For functions marked with an asterix, there are additional family members with the suffices, f and l.If you do not support POSIX tracing, then answer No for those functions. If the error handling is different for those please add details in the Appendix at the end of this questionnaire.
Function Error Detected access() EINVAL Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ETXTBSY Enter_Yes_or_No chdir() ENAMETOOLONG Enter_Yes_or_No ELOOP Enter_Yes_or_No clock_settime() EPERM Enter_Yes_or_No close() EIO Enter_Yes_or_No closedir() EBADF Enter_Yes_or_No EINTR Enter_Yes_or_No erfc() * Range Error Enter_Yes_or_No exp() * Range Error Enter_Yes_or_No exp2() * Range Error Enter_Yes_or_No expm1() * Range Error Enter_Yes_or_No fchdir() EINTR Enter_Yes_or_No EIO Enter_Yes_or_No fclose() ENXIO Enter_Yes_or_No fcntl() EDEADLK Enter_Yes_or_No fdim() * Range Error Enter_Yes_or_No fdopen() EBADF Enter_Yes_or_No EINVAL Enter_Yes_or_No EMFILE Enter_Yes_or_No ENOMEM Enter_Yes_or_No fflush() ENXIO Enter_Yes_or_No fgetc() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No fgetpos() EBADF Enter_Yes_or_No ESPIPE Enter_Yes_or_No fgetwc() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No fileno() EBADF Enter_Yes_or_No fmod() * Range Error Enter_Yes_or_No fopen() EINVAL Enter_Yes_or_No ELOOP Enter_Yes_or_No EMFILE Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ENOMEN Enter_Yes_or_No ETXTBSY Enter_Yes_or_No fpathconf() EBADF Enter_Yes_or_No EINVAL Enter_Yes_or_No fputc() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No fread() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No freopen() EINVAL Enter_Yes_or_No ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No ETXTBSY Enter_Yes_or_No fscanf() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No fstat() EOVERFLOW Enter_Yes_or_No ftell() ESPIPE Enter_Yes_or_No getcwd() EACCES Enter_Yes_or_No ENOMEM Enter_Yes_or_No ldexp() * Range Error Enter_Yes_or_No link() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No mkdir() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No mktime() EOVERFLOW Enter_Yes_or_No mlock() EINVAL Enter_Yes_or_No ENOMEM Enter_Yes_or_No munlock() EINVAL Enter_Yes_or_No mlockall() ENOMEM Enter_Yes_or_No ENOPERM Enter_Yes_or_No mq_getattr() EBADF Enter_Yes_or_No mq_receive() EBADF Enter_Yes_or_No mq_timedreceive() EBADF Enter_Yes_or_No open() EAGAIN Enter_Yes_or_No EINVAL Enter_Yes_or_No ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ETXTBSY Enter_Yes_or_No opendir() ELOOP Enter_Yes_or_No EMFILE Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ENFILE Enter_Yes_or_No pathconf() EACCES Enter_Yes_or_No EINVAL Enter_Yes_or_No ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ENOENT Enter_Yes_or_No ENOTDIR Enter_Yes_or_No posix_trace_attr_destroy() EINVAL Enter_Yes_or_No posix_trace_attr_getclockres() EINVAL Enter_Yes_or_No posix_trace_attr_getcreatetime() EINVAL Enter_Yes_or_No posix_trace_attr_getgenversion() EINVAL Enter_Yes_or_No posix_trace_attr_getname() EINVAL Enter_Yes_or_No posix_trace_attr_getinherited() EINVAL Enter_Yes_or_No posix_trace_attr_getlogfullpolicy() EINVAL Enter_Yes_or_No posix_trace_attr_getstreamfullpolicy() EINVAL Enter_Yes_or_No posix_trace_attr_setinherited() EINVAL Enter_Yes_or_No posix_trace_attr_setlogfullpolicy() EINVAL Enter_Yes_or_No posix_trace_attr_setstreamfullpolicy() EINVAL Enter_Yes_or_No posix_trace_attr_getlogsize() EINVAL Enter_Yes_or_No posix_trace_attr_getmaxdatasize() EINVAL Enter_Yes_or_No posix_trace_attr_getmaxsystemeventsize() EINVAL Enter_Yes_or_No posix_trace_attr_getmaxusereventsize() EINVAL Enter_Yes_or_No posix_trace_attr_getstreamsize() EINVAL Enter_Yes_or_No posix_trace_attr_setlogsize() EINVAL Enter_Yes_or_No posix_trace_attr_setstreamsize() EINVAL Enter_Yes_or_No posix_trace_close() EINVAL Enter_Yes_or_No posix_trace_rewind() EINVAL Enter_Yes_or_No posix_trace_eventset_add() EINVAL Enter_Yes_or_No posix_trace_eventset_del() EINVAL Enter_Yes_or_No posix_trace_eventset_empty() EINVAL Enter_Yes_or_No posix_trace_eventset_fill() EINVAL Enter_Yes_or_No posix_trace_eventset_ismember() EINVAL Enter_Yes_or_No pow() * Range Error Enter_Yes_or_No pthread_attr_destroy() EINVAL Enter_Yes_or_No pthread_attr_init() EBUSY Enter_Yes_or_No pthread_attr_getdetachstate() EINVAL Enter_Yes_or_No pthread_attr_setdetachstate() EINVAL Enter_Yes_or_No pthread_attr_getguardsize() EINVAL Enter_Yes_or_No pthread_attr_setguardsize() EINVAL Enter_Yes_or_No pthread_attr_getinheritsched() EINVAL Enter_Yes_or_No pthread_attr_setinheritsched() EINVAL Enter_Yes_or_No ENOSUP Enter_Yes_or_No pthread_attr_getschedparam() EINVAL Enter_Yes_or_No pthread_attr_setschedparam() EINVAL Enter_Yes_or_No ENOSUP Enter_Yes_or_No pthread_attr_getschedpolicy() EINVAL Enter_Yes_or_No pthread_attr_setschedpolicy() EINVAL Enter_Yes_or_No ENOSUP Enter_Yes_or_No pthread_attr_getscope() EINVAL Enter_Yes_or_No pthread_attr_setscope() EINVAL Enter_Yes_or_No ENOSUP Enter_Yes_or_No pthread_attr_getstack() EINVAL Enter_Yes_or_No pthread_attr_setstack() EINVAL Enter_Yes_or_No EBUSY Enter_Yes_or_No pthread_attr_getstackaddr() EINVAL Enter_Yes_or_No pthread_attr_setstackaddr() EINVAL Enter_Yes_or_No pthread_attr_getstacksize() EINVAL Enter_Yes_or_No pthread_attr_setstacksize() EINVAL Enter_Yes_or_No pthread_cancel() ESRCH Enter_Yes_or_No pthread_cond_broadcast() EINVAL Enter_Yes_or_No pthread_cond_signal() EINVAL Enter_Yes_or_No pthread_cond_destroy() EBUSY Enter_Yes_or_No EINVAL Enter_Yes_or_No pthread_cond_init() EBUSY Enter_Yes_or_No EINVAL Enter_Yes_or_No pthread_cond_timedwait() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_cond_wait() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_condattr_destroy() EINVAL Enter_Yes_or_No pthread_condattr_getclock() EINVAL Enter_Yes_or_No pthread_condattr_setclock() EINVAL Enter_Yes_or_No pthread_condattr_getpshared() EINVAL Enter_Yes_or_No pthread_condattr_setpshared() EINVAL Enter_Yes_or_No pthread_create() EINVAL Enter_Yes_or_No pthread_detach() EINVAL Enter_Yes_or_No ESRCH Enter_Yes_or_No pthread_getcpuclockid() ESRCH Enter_Yes_or_No pthread_getschedparam() ESRCH Enter_Yes_or_No pthread_setschedparam() EINVAL Enter_Yes_or_No ENOTSUP Enter_Yes_or_No EPERM Enter_Yes_or_No ESRCH Enter_Yes_or_No pthread_setspecific() ESRCH Enter_Yes_or_No pthread_join() EDEADLK Enter_Yes_or_No EINVAL Enter_Yes_or_No pthread_keydelete() EINVAL Enter_Yes_or_No pthread_mutex_destroy() EBUSY Enter_Yes_or_No EINVAL Enter_Yes_or_No pthread_mutex_init() EBUSY Enter_Yes_or_No EINVAL Enter_Yes_or_No pthread_mutex_lock() EINVAL Enter_Yes_or_No EDEADLK Enter_Yes_or_No pthread_mutex_trylock() EINVAL Enter_Yes_or_No pthread_mutex_unlock() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_mutex_timedlock() EINVAL Enter_Yes_or_No EDEADLK Enter_Yes_or_No pthread_mutexattr_destroy() EINVAL Enter_Yes_or_No pthread_mutexattr_getprioceiling() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_mutexattr_setprioceiling() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_mutexattr_getprotocol() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_mutexattr_setprotocol() EINVAL Enter_Yes_or_No EPERM Enter_Yes_or_No pthread_mutexattr_getpshared() EINVAL Enter_Yes_or_No pthread_mutexattr_setpshared() EINVAL Enter_Yes_or_No pthread_mutexattr_gettype() EINVAL Enter_Yes_or_No pthread_mutexattr_settype() EINVAL Enter_Yes_or_No pthread_once() EINVAL Enter_Yes_or_No pthread_setcancelstate() EINVAL Enter_Yes_or_No pthread_setcanceltype() EINVAL Enter_Yes_or_No pthread_schedprio() EINVAL Enter_Yes_or_No ENOTSUP Enter_Yes_or_No EPERM Enter_Yes_or_No ESRCH Enter_Yes_or_No putc() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No putchar() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No puts() ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No read() EIO Enter_Yes_or_No ENOBUFS Enter_Yes_or_No ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No readdir() EBADF Enter_Yes_or_No ENOENT Enter_Yes_or_No remove() EBUSY Enter_Yes_or_No ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ETXTBSY Enter_Yes_or_No rename() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ETXTBSY Enter_Yes_or_No rmdir() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No sem_close() EINVAL Enter_Yes_or_No sem_destroy() EINVAL Enter_Yes_or_No EBUSY Enter_Yes_or_No sem_getvalue() EINVAL Enter_Yes_or_No sem_post() EINVAL Enter_Yes_or_No sem_timedwait() EDEADLK Enter_Yes_or_No EINTR Enter_Yes_or_No EINVAL Enter_Yes_or_No sem_trywait() EDEADLK Enter_Yes_or_No EINTR Enter_Yes_or_No EINVAL Enter_Yes_or_No sem_wait() EDEADLK Enter_Yes_or_No EINTR Enter_Yes_or_No EINVAL Enter_Yes_or_No setvbuf() EBADF Enter_Yes_or_No sigaction() EINVAL Enter_Yes_or_No sigaddset() EINVAL Enter_Yes_or_No sigdelset() EINVAL Enter_Yes_or_No sigismember() EINVAL Enter_Yes_or_No signal() EINVAL Enter_Yes_or_No sigtimedwait() EINVAL Enter_Yes_or_No sigwait() EINVAL Enter_Yes_or_No sigwaitinfo() EINVAL Enter_Yes_or_No stat() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No EOVERFLOW Enter_Yes_or_No strcoll() EINVAL Enter_Yes_or_No strerror() EINVAL Enter_Yes_or_No strerror_r() ERANGE Enter_Yes_or_No strtod() EINVAL Enter_Yes_or_No strtoimax() EINVAL Enter_Yes_or_No strtol() EINVAL Enter_Yes_or_No strtoul() EINVAL Enter_Yes_or_No strtoumax() EINVAL Enter_Yes_or_No strxfrm() EINVAL Enter_Yes_or_No timer_delete() EINVAL Enter_Yes_or_No timer_getoverrun() EINVAL Enter_Yes_or_No timer_gettime() EINVAL Enter_Yes_or_No timer_settime() EINVAL Enter_Yes_or_No tmpfile() EMFILE Enter_Yes_or_No ENOMEM Enter_Yes_or_No unlink() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No ETXTBSY Enter_Yes_or_No utime() ELOOP Enter_Yes_or_No ENAMETOOLONG Enter_Yes_or_No vfscanf() EILSEQ Enter_Yes_or_No EINVAL Enter_Yes_or_No ENOMEM Enter_Yes_or_No ENXIO Enter_Yes_or_No write() ENETDOWN Enter_Yes_or_No ENETUNREACH Enter_Yes_or_No ENXIO Enter_Yes_or_No
Rationale
Each of the above error conditions is marked as optional in the System Interfaces Volume and an implementation may return this error in the circumstances specified or may not provide the error indication.
Reference
IEEE Std 1003.1, 2003 Edition, the System Interfaces Volume, Section 2.3, Error Numbers.
Question SI-9: What format of floating-point numbers is supported by this implementation?
Response
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
IEEE Std 1003.1, 2003 Edition, the System Interfaces Volume, Section 1.7, Relationship to Other Formal Standards.
Question SI-10: Which floating-point exceptions are supported by this implementation for the fegetexecptflag(), feraiseexcept(), fesetexecptflag(), and fetestexecptflag() functions?
Response
Provide a list of the floating-point exceptions using the constant names in the <fenv.h> header.
Rationale
The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <fenv.h>.
Question SI-11: Which floating-point rounding directions are supported by this implementation for the fegetround(), and fesetround() functions?
Response
Provide a list of the floating-point round modes using the constant names in the <fenv.h> header.
Rationale
The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <fenv.h>.
Question SI-12: Is a non-stop floating-point exception mode supported by this implementation?
Response
Enter_Yes_or_No
Rationale
The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.
Reference
IEEE Std 1003.1, 2003 Edition, the System Interfaces Volume, Chapter 3, System Interfaces, feholdexcept().
Question SI-13: 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 Conformance Document", or provide a detailed description of the access control mechanisms on your implementation.
Rationale
the System Interfaces Volume notes that implementations may provide additional or alternate file access control mechanisms, or both.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 4, General Concepts, Section 4.4, File Access Permissions.
Question SI-14: Are any additional or alternate file access control mechanisms implemented that could cause fstat() or stat() to fail?
Response
Enter_Yes_or_No
If you answered Yes above, Either indicate below that the reader should "Refer to the POSIX Conformance Document", or provide a detailed description of the additional or alternate access mechanisms on your implementation that would cause fstat() or stat() to fail.
Rationale
the System Interfaces Volume 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
IEEE Std 1003.1, 2003 Edition, the System Interfaces Volume, Chapter 3, System Interfaces, fstat() and stat().
Question SI-15: What coded character sets are supported by the implementation?
Response
Enter your response in the area below:
Rationale
The Base Definitions Volume states that conforming implementations support one or more coded character sets, and that each of these includes the portable character set.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 6, Character Set.
Question SI-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. If the implementation does use ISO 8859-1:1987, just enter "ISO 8859-1:1987" below.
Rationale
It is useful to be aware of the underlying codeset of the implementation.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 6, Character Set.
Question SI-17: 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 System Interfaces, Section 2.9.5.2. List below the functions which have cancellation points in your implementation.
Rationale
IEEE Std 1003.1, 2003 Edition, Base Definitions Volume, states that a cancellation point may occur for these functions.
Reference
IEEE Std 1003.1, 2003 Edition, System Interfaces Volume, Section 2.9.5.2, Cancellation Points.
Question SI-18: Which file types does the implementation support _POSIX_PRIORITIZED_IO on?
Response
List below the file types that the system supports _POSIX_PRIORITIZED_IO on
Rationale
Reference
Technical Standard, IEEE Std 1003.1, 2003 Edition, Base Definitions Volume, Section 2.1.5.2 IEEE Std 1003.1, 2003 Edition, System Interfaces Volume, Section 2.8
Question SI-19: What scheduling policy is associated with SCHED_OTHER?
Response
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(), or a reference to available system documentation.
Rationale
IEEE Std 1003.1, 2003 Edition, Base Definitions Volume, states that conforming implementations must support a scheduling policy identified as SCHED_OTHER but define its effects as implementation-defined.
Reference
IEEE Std 1003.1, 2003 Edition, System Interfaces Volume, Section 2.8.4, Scheduling Policies.
Question SI-20: What scheduling contention scopes are supported: PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both?
Response
Enter below PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM or both PTHREAD_SCOPE_PROCESS and PTHREAD_SCOPE_SYSTEM.
Rationale
System Interfaces, Issue 6 states that conforming implementations will support PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both.
Reference
IEEE Std 1003.1, 2003 Edition, System Interfaces Volume, Section 2.9.4, Thread Scheduling Contention Scope.
Question SI-21: What is the default scheduling contention scope when a thread is created?
Response
State below either PTHREAD_SCOPE_PROCESS or PTHREAD_SCOPE_SYSTEM.
Rationale
The specification defines the default scheduling contention scope as implementation-defined.
Reference
IEEE Std 1003.1, 2003 Edition, System Interfaces Volume, Section 2.9.4, Thread Scheduling Attributes.
Question SI-22: What is the mechanism to configure the system so that the scheduling allocation domain has size one, so that the binding of threads to scheduling allocation domains remains static?
Response
Enter a response below
Rationale
An implementation conforming to PSE52 shall provide a mechanism to configure the system so that the scheduling allocation domain has size one, and so that the binding of threads to scheduling allocation domains remains static. The mechanism by which this requirement is achieved shall be implementation defined.
Reference
IEEE Std 1003.13, 2003 Edition, Section 7, Realtime Controller System Profile (PSE52).
Question SI-23: 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.Enter_Yes_or_No 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.Enter_Yes_or_No The implementation provides a C-language compilation environment with
32-bit int, and 64-bit long, pointer and off_t types.Enter_Yes_or_No 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.Enter_Yes_or_No
Rationale
The Base Definitions Volume defines these scenarios as possible C-language compilation environment offerings.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <unistd.h>.
Question SI-24: 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.Enter_Yes_or_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.Enter_Yes_or_No The implementation provides an execution environment with
32-bit int, and 64-bit long, pointer and off_t types.Enter_Yes_or_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.Enter_Yes_or_No
Rationale
The Base Definitions Volume defines four scenarios as possible C-language compilation environment offerings but does not define which corresponding execution environments are supported.
Reference
IEEE Std 1003.1, 2003 Edition, The Base Definitions Volume, Chapter 13, Headers, <unistd.h>.
Question SI-25: What is the largest type that can be stored in type off_t ?
Response
Rationale
The type off_t shall be capable of storing any value contained in type long.
Reference
IEEE Std 1003.13-2003, Section 9.2.1 POSIX.1 Interfaces (C Language Option).
| Date | Name | Comment |
|---|---|---|
| New | ||