Conformance Statement
|
|
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 | QNX Software Systems GmbH & Co. KG |
|---|---|
| Author | Sunil Kittur |
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 |
|---|---|---|
| QNX Neutrino RTOS | 6.4 | QNX Software Systems GmbH & Co. KG |
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 |
|---|---|
| Platform Specific Certification |
Not Applicable |
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 |
|---|---|
|
QNX Neutrino RTOS 6.4 on Intel PC.
Intel x86 processor, 1GB RAM, 160GB disk. |
Test Suite Name:
VSPSE52-2003 Test Suite Version: 1.0 |
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.
Contact Kerry Johnson at QNX Software Systems: kjohnson@qnx.com, +1 613 271 9259.
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. Yes
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 No _POSIX_TRACE_EVENT_LOG No _POSIX_TRACE_LOG No POSIX 1003.26-2003 No POSIX.5c Interfaces (Ada Language Option) 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
_POSIX_ASYNCHRONOUS_IO
_POSIX_BARRIERS
_POSIX_CHOWN_RESTRICTED
_POSIX_IPV6
_POSIX_MEMORY_PROTECTION
_POSIX_PRIORITIZED_IO
_POSIX_RAW_SOCKETS
_POSIX_SAVED_IDS
_POSIX_SPORADIC_SERVER
_POSIX_THREAD_PROCESS_SHARED
_POSIX_TYPED_MEMORY_OBJECTS
POSIX_C_LANG_WIDE_CHAR
POSIX_DEVICE_SPECIFIC
POSIX_EVENT_MGMT
POSIX_FIFO
POSIX_FILE_ATTRIBUTES
POSIX_FILE_SYSTEM_EXT
POSIX_JOB_CONTROL
POSIX_MULTI_PROCESS
POSIX_NETWORKING
POSIX_PIPE
POSIX_REGEXP
POSIX_RW_LOCKS
POSIX_SHELL_FUNCS
POSIX_SIGNAL_JUMP
POSIX_STRING_MATCHING
POSIX_SYMBOLIC_LINKS
POSIX_SYSTEM_DATABASE
POSIX_USER_GROUPS
POSIX_WIDE_CHAR_IO
XSI_C_LANG_SUPPORT
XSI_DEVICE_IO
XSI_DYNAMIC_LINKING
XSI_FD_MGMT
XSI_FILE_SYSTEM
XSI_JOB_CONTROL
XSI_JUMP
XSI_MULTI_PROCESS
XSI_SINGLE_PROCESS
XSI_SYSTEM_DATABASE
XSI_SYSTEM_LOGGING
XSI_TIMERS
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. 2 FLT_MANT_DIG Number of base-FLT_RADIX digits in the float significand. 24 DBL_MANT_DIG Number of base-FLT_RADIX digits in the double significand. 53 LDBL_MANT_DIG Number of base-FLT_RADIX digits in the long double significand. 64 FLT_DIG Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a float representation and back again without change to the q digits. 6 DBL_DIG Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a double representation and back again without change to the q digits. 15 LDBL_DIG Number of decimal digits, q, such that any floating-point number with q digits can be rounded into a long double representation and back again without change to the q digits. 18 FLT_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised float. -125 DBL_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised double. -1021 LDBL_MIN_EXP Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised long double. -16381 FLT_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised floats. -37 DBL_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised doubles. -307 LDBL_MIN_10_EXP Minimum negative integer such that 10 raised to that power is in the range of normalised long doubles. -4931 FLT_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite float. 128 DBL_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite double. 1024 LDBL_MAX_EXP Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite long double. 16384 FLT_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite floats. 38 DBL_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite doubles. 308 LDBL_MAX_10_EXP Maximum integer such that 10 raised to that power is in the range of representable finite long doubles. 4932 FLT_MAX Maximum representable finite float. 3.40282347e+38 DBL_MAX Maximum representable finite double. 1.7976931348623157e308 LDBL_MAX Maximum representable finite long double. 1.189731495357231765e+4932 FLT_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a float. 1.1920929e-07 DBL_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a double. 2.2204460492503131e-16 LDBL_EPSILON Difference between 1.0 and the least value greater than 1.0 that is representable as a long double. 1.084202172485504434e-19 FLT_MIN Minimum normalised positive float. 1.17549435e-38 DBL_MIN Minimum normalised positive double. 2.2250738585072014e-308 LDBL_MIN Minimum normalised positive long double. 3.362103143112093506e-4932
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. 1048576 1048576 FILESIZEBITS Minimum number of bits needed to represent as a signed integer value the maximum size of a regular file. 32 64 LINK_MAX Maximum number of links to a single file. 1 2147483647 MQ_OPEN_MAX The maximum number of open message queue descriptors a process may hold. 8 1024 MQ_PRIO_MAX The maximum number of message priorities supported by the implementation. 32 32 NAME_MAX Maximum number of bytes in a filename (not including terminating null). 91 255 OPEN_MAX Maximum number of open files that one process can have open at any one time. 100 65534 PAGESIZE Size of a page in bytes. 4096 4096 PATH_MAX Maximum number of bytes in a pathname (including the terminating null). 255 1024 PTHREAD_DESTRUCTOR_ITERATIONS Maximum number of attempts made to destroy a thread's thread-specific data values on thread exit. 4 4 PTHREAD_KEYS_MAX Maximum number of data keys that can be created by a process. 128 128 PTHREAD_STACK_MIN Minimum size in bytes of thread stack storage. 256 256 PTHREAD_THREADS_MAX Maximum number of threads that can be created per process. 65534 65534 RTSIG_MAX Maximum number of realtime signals reserved for application use in this implementation. 16 16 SEM_NSEMS_MAX Maximum number of semaphores that a process may have. Unlimited Unlimited SEM_VALUE_MAX The maximum value a semaphore may have. 1073741823 1073741823 SIGQUEUE_MAX Maximum number of queued signals that a process may send and have pending at the receiver(s) at any time. Unlimited Unlimited SS_REPL_MAX The maximum number of replenishment operations that may be simultaneously pending for a particular sporadic server scheduler. 65535 65535 STREAM_MAX Number of streams that one process can have open at one time. Unlimited Unlimited TIMER_MAX Maximum number of timers per process supported by the implementation. 65534 65534 TRACE_EVENT_NAME_MAX Maximum length of the trace event name. Not Supported Not Supported TRACE_NAME_MAX Maximum length of the trace generation version string or of the trace stream name. Not Supported Not Supported TRACE_SYS_MAX Maximum number of trace streams that may simultaneously exist in the system. Not Supported Not Supported 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. Not Supported Not Supported TZNAME_MAX Maximum number of bytes supported for the name of a time zone. 30 30
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. 127 INT_MAX Maximum value of an int. 2147483647 LONG_MAX Maximum value of a long int. 2147483647 LLONG_MAX Maximum value of a long long. 9223372036854775807 SHRT_MAX Maximum value of a short. 32767 SSIZE_MAX Maximum value of an object of type ssize_t. 2147483647 UINT_MAX Maximum value of an unsigned int. 4294967295 ULONG_MAX Maximum value of an unsigned long int. 4294967295 ULLONG_MAX Maximum value of a unigsned long long. 18446744073709551615 USHRT_MAX Maximum value of an unsigned short int. 65535
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. 255 FOPEN_MAX Number of streams which the implementation guarantees can be open simultaneously. 16 L_tmpnam Maximum size of character array to hold tmpnam() output. 255 TMP_MAX Minimum number of unique filenames generated by tmpnam(), which is the maximum number of times an application can call tmpnam() reliably. 17576
Rationale
This set of constants provides useful information about the implementation.
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 Yes ENAMETOOLONG Yes ETXTBSY No chdir() ENAMETOOLONG Yes ELOOP Yes clock_settime() EPERM Yes close() EIO Yes closedir() EBADF Yes EINTR Yes erfc() * Range Error Yes exp() * Range Error Yes exp2() * Range Error Yes expm1() * Range Error Yes fchdir() EINTR Yes EIO No fclose() ENXIO No fcntl() EDEADLK Yes fdim() * Range Error Yes fdopen() EBADF No EINVAL Yes EMFILE No ENOMEM Yes fflush() ENXIO Yes fgetc() ENOMEM No ENXIO Yes fgetpos() EBADF Yes ESPIPE Yes fgetwc() ENOMEM No ENXIO Yes fileno() EBADF No fmod() * Range Error Yes fopen() EINVAL Yes ELOOP Yes EMFILE Yes ENAMETOOLONG Yes ENOMEN Yes ETXTBSY Yes fpathconf() EBADF Yes EINVAL Yes fputc() ENOMEM No ENXIO Yes fread() ENOMEM No ENXIO Yes freopen() EINVAL Yes ELOOP Yes ENAMETOOLONG Yes ENOMEM Yes ENXIO Yes ETXTBSY Yes fscanf() ENOMEM No ENXIO Yes fstat() EOVERFLOW Yes ftell() ESPIPE Yes getcwd() EACCES Yes ENOMEM Yes ldexp() * Range Error Yes link() ELOOP Yes ENAMETOOLONG Yes mkdir() ELOOP Yes ENAMETOOLONG Yes mktime() EOVERFLOW No mlock() EINVAL Yes ENOMEM Yes munlock() EINVAL Yes mlockall() ENOMEM Yes ENOPERM Yes mq_getattr() EBADF Yes mq_receive() EBADF Yes mq_timedreceive() EBADF Yes open() EAGAIN No EINVAL Yes ELOOP Yes ENAMETOOLONG Yes ETXTBSY Yes opendir() ELOOP Yes EMFILE Yes ENAMETOOLONG Yes ENFILE Yes pathconf() EACCES Yes EINVAL Yes ELOOP Yes ENAMETOOLONG Yes ENOENT Yes ENOTDIR Yes posix_trace_attr_destroy() EINVAL No posix_trace_attr_getclockres() EINVAL No posix_trace_attr_getcreatetime() EINVAL No posix_trace_attr_getgenversion() EINVAL No posix_trace_attr_getname() EINVAL No posix_trace_attr_getinherited() EINVAL No posix_trace_attr_getlogfullpolicy() EINVAL No posix_trace_attr_getstreamfullpolicy() EINVAL No posix_trace_attr_setinherited() EINVAL No posix_trace_attr_setlogfullpolicy() EINVAL No posix_trace_attr_setstreamfullpolicy() EINVAL No posix_trace_attr_getlogsize() EINVAL No posix_trace_attr_getmaxdatasize() EINVAL No posix_trace_attr_getmaxsystemeventsize() EINVAL No posix_trace_attr_getmaxusereventsize() EINVAL No posix_trace_attr_getstreamsize() EINVAL No posix_trace_attr_setlogsize() EINVAL No posix_trace_attr_setstreamsize() EINVAL No posix_trace_close() EINVAL No posix_trace_rewind() EINVAL No posix_trace_eventset_add() EINVAL No posix_trace_eventset_del() EINVAL No posix_trace_eventset_empty() EINVAL No posix_trace_eventset_fill() EINVAL No posix_trace_eventset_ismember() EINVAL No pow() * Range Error Yes pthread_attr_destroy() EINVAL No pthread_attr_init() EBUSY No pthread_attr_getdetachstate() EINVAL No pthread_attr_setdetachstate() EINVAL No pthread_attr_getguardsize() EINVAL No pthread_attr_setguardsize() EINVAL No pthread_attr_getinheritsched() EINVAL No pthread_attr_setinheritsched() EINVAL No ENOSUP No pthread_attr_getschedparam() EINVAL No pthread_attr_setschedparam() EINVAL No ENOSUP No pthread_attr_getschedpolicy() EINVAL No pthread_attr_setschedpolicy() EINVAL No ENOSUP No pthread_attr_getscope() EINVAL No pthread_attr_setscope() EINVAL Yes ENOSUP Yes pthread_attr_getstack() EINVAL No pthread_attr_setstack() EINVAL No EBUSY No pthread_attr_getstackaddr() EINVAL No pthread_attr_setstackaddr() EINVAL No pthread_attr_getstacksize() EINVAL No pthread_attr_setstacksize() EINVAL No pthread_cancel() ESRCH Yes pthread_cond_broadcast() EINVAL Yes pthread_cond_signal() EINVAL Yes pthread_cond_destroy() EBUSY Yes EINVAL Yes pthread_cond_init() EBUSY Yes EINVAL Yes pthread_cond_timedwait() EINVAL Yes EPERM Yes pthread_cond_wait() EINVAL Yes EPERM Yes pthread_condattr_destroy() EINVAL No pthread_condattr_getclock() EINVAL No pthread_condattr_setclock() EINVAL No pthread_condattr_getpshared() EINVAL No pthread_condattr_setpshared() EINVAL No pthread_create() EINVAL Yes pthread_detach() EINVAL Yes ESRCH Yes pthread_getcpuclockid() ESRCH Yes pthread_getschedparam() ESRCH Yes pthread_setschedparam() EINVAL Yes ENOTSUP Yes EPERM Yes ESRCH Yes pthread_setspecific() ESRCH No pthread_join() EDEADLK Yes EINVAL Yes pthread_keydelete() EINVAL Yes pthread_mutex_destroy() EBUSY Yes EINVAL Yes pthread_mutex_init() EBUSY Yes EINVAL Yes pthread_mutex_lock() EINVAL Yes EDEADLK Yes pthread_mutex_trylock() EINVAL Yes pthread_mutex_unlock() EINVAL Yes EPERM Yes pthread_mutex_timedlock() EINVAL Yes EDEADLK Yes pthread_mutexattr_destroy() EINVAL No pthread_mutexattr_getprioceiling() EINVAL No EPERM No pthread_mutexattr_setprioceiling() EINVAL Yes EPERM No pthread_mutexattr_getprotocol() EINVAL No EPERM No pthread_mutexattr_setprotocol() EINVAL Yes EPERM No pthread_mutexattr_getpshared() EINVAL No pthread_mutexattr_setpshared() EINVAL No pthread_mutexattr_gettype() EINVAL No pthread_mutexattr_settype() EINVAL Yes pthread_once() EINVAL No pthread_setcancelstate() EINVAL Yes pthread_setcanceltype() EINVAL Yes pthread_schedprio() EINVAL Yes ENOTSUP No EPERM Yes ESRCH Yes putc() ENOMEM No ENXIO Yes putchar() ENOMEM No ENXIO Yes puts() ENOMEM No ENXIO Yes read() EIO Yes ENOBUFS Yes ENOMEM Yes ENXIO Yes readdir() EBADF Yes ENOENT No remove() EBUSY No ELOOP Yes ENAMETOOLONG Yes ETXTBSY No rename() ELOOP Yes ENAMETOOLONG Yes ETXTBSY No rmdir() ELOOP Yes ENAMETOOLONG Yes sem_close() EINVAL Yes sem_destroy() EINVAL Yes EBUSY Yes sem_getvalue() EINVAL Yes sem_post() EINVAL Yes sem_timedwait() EDEADLK No EINTR Yes EINVAL Yes sem_trywait() EDEADLK No EINTR Yes EINVAL Yes sem_wait() EDEADLK No EINTR Yes EINVAL Yes setvbuf() EBADF No sigaction() EINVAL Yes sigaddset() EINVAL Yes sigdelset() EINVAL Yes sigismember() EINVAL Yes signal() EINVAL Yes sigtimedwait() EINVAL Yes sigwait() EINVAL No sigwaitinfo() EINVAL No stat() ELOOP Yes ENAMETOOLONG Yes EOVERFLOW Yes strcoll() EINVAL No strerror() EINVAL No strerror_r() ERANGE Yes strtod() EINVAL Yes strtoimax() EINVAL Yes strtol() EINVAL Yes strtoul() EINVAL Yes strtoumax() EINVAL Yes strxfrm() EINVAL No timer_delete() EINVAL Yes timer_getoverrun() EINVAL Yes timer_gettime() EINVAL Yes timer_settime() EINVAL Yes tmpfile() EMFILE Yes ENOMEM Yes unlink() ELOOP Yes ENAMETOOLONG Yes ETXTBSY No utime() ELOOP Yes ENAMETOOLONG Yes vfscanf() EILSEQ Yes EINVAL No ENOMEM No ENXIO Yes write() ENETDOWN Yes ENETUNREACH Yes ENXIO Yes
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.
IEEE 754 in hardware
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.
FE_DIVBYZERO
FE_INEXACT
FE_INVALID
FE_OVERFLOW
FE_UNDERFLOW
Rationale
The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.
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.
FE_DOWNWARD
FE_TONEAREST
FE_TOWARDZERO
FE_UPWARD
Rationale
The behavior of a conforming implementation in this area is not mandated in the specification and needs to be defined.
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
Yes
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.
Standard access control is provided. Refer to the POSIX Conformance Document.
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
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:
ISO 8859-1:1987
ISO 10646-1:2000
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.
ISO 8859-1:1987
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.
closedir()
closelog()
dlopen()
endgrent()
endhostent()
endnetent()
endprotoent()
endpwent()
endservent()
fclose()
fflush()
fgetc()
fgetpos()
fgets()
fgetwc()
fgetws()
fopen()
fprintf()
fputc()
fputwc()
fputws()
fread()
freopen()
fscanf()
fseek()
fseeko()
fsetpos()
ftell()
ftello()
ftw()
fwprintf()
fwrite()
fwscanf()
getc()
getc_unlocked()
getchar()
getchar_unlocked()
getgrent()
getgrgid()
getgrgid_r()
getgrnam()
getgrnam_r()
getlogin()
getlogin_r()
getnetbyaddr()
getnetbyname()
getnetent()
getprotobyname()
getprotobynumber()
getprotoent()
getpwent()
getpwent_r()
getpwnam()
getpwnam_r()
getpwuid()
getpwuid_r()
gets()
getservbyname()
getservbyport()
getservent()
getwc()
getwchar()
getwd()
glob()
ioctl()
lseek()
mkstemp()
nftw()
opendir()
openlog()
pathconf()
pclose()
perror()
popen()
posix_fadvise()
posix_fallocate()
posix_openpt()
posix_spawn()
posix_spawnp()
printf()
pthread_rwlock_rdlock()
pthread_rwlock_timedrdlock()
pthread_rwlock_timedwrlock()
pthread_rwlock_wrlock()
putc()
putc_unlocked()
putchar()
putchar_unlocked()
puts()
putwc()
putwchar()
readdir()
readdir_r()
rewind()
scanf()
seekdir()
setgrent()
sethostent()
setnetent()
setprotoent()
setpwent()
setservent()
syslog()
tmpfile()
vfprintf()
vfwprintf()
vprintf()
vwprintf()
wscanf()
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
Regular files.
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.
SCHED_RR
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.
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.
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
For a multiprocessor, the number of processors enabled is controlled by the BSP specific startup program.
The -P1 command line argument to the startup program enables only one processor, creating a scheduling allocation domain of size one.
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.Yes The implementation provides a C-language compilation environment with
32-bit int, long and pointer types and an off_t type using at least 64 bits.Yes The implementation provides a C-language compilation environment with
32-bit int, and 64-bit long, pointer and off_t types.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.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.Yes The implementation provides an execution environment with
32-bit int, long and pointer types and an off_t type using at least 64 bits.Yes The implementation provides an execution environment with
32-bit int, and 64-bit long, pointer and off_t types.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.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
long long
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).
The build file must specify procnto -m~b to perform POSIX error checking for arguments to mapped file operations.
The POSIXLY_CORRECT environment variable must be set to 1.
The compiler must be explicitly configured for C99 compatibility. For example, with a gcc-4.2.1 compiler:
qcc -V4.2.1,gcc_ntox86 -Wc,-std=c99
| Date | Name | Comment |
|---|---|---|
| New | ||