|
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 |
Wind River Systems, Inc. |
|
Author |
Pierre-Alain Darlet |
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 |
|
VxWorks |
6.4 |
Wind River Systems, Inc. |
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 |
|
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 |
|
VxWorks 6.4's Real Time Process environment , on a Motorola MVME5500 board equipped with a PowerPC 7455 processor. |
Test Suite Name: VSPSE52-2003
|
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_ |
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 |
Yes |
|
_POSIX_TRACE_EVENT_LOG |
Yes |
|
_POSIX_TRACE_LOG |
Yes |
|
POSIX 1003.26-2003 |
Yes |
|
POSIX.5c Interfaces ( |
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. |
2 |
|
FLT_ |
Number of base-FLT_RADIX digits in the float significand. |
24 |
|
DBL_ |
Number of base-FLT_RADIX digits in the double significand. |
53 |
|
LDBL_ |
Number of base-FLT_RADIX digits in the long double significand. |
53 |
|
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. |
15 |
|
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. |
-1021 |
|
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. |
-307 |
|
FLT_ |
Maximum integer such that FLT_RADIX raised
to that power minus 1 is a representable finite
float. |
128 |
|
DBL_ |
Maximum integer such that FLT_RADIX raised
to that power minus 1 is a representable finite
double. |
1024 |
|
LDBL_ |
Maximum integer such that FLT_RADIX raised
to that power minus 1 is a representable finite
long double. |
1024 |
|
FLT_ |
Maximum integer such that 10 raised
to that power is in the range of representable
finite floats. |
38 |
|
DBL_ |
Maximum integer such that 10 raised
to that power is in the range of representable
finite doubles. |
308 |
|
LDBL_ |
Maximum integer such that 10 raised
to that power is in the range of representable
finite long doubles. |
308 |
|
FLT_ |
Maximum representable finite
float. |
3.40282347E38 |
|
DBL_ |
Maximum representable finite
double. |
1.7976931348623157E308 |
|
LDBL_ |
Maximum representable finite
long double. |
1.7976931348623157E308 |
|
FLT_EPSILON |
Difference between 1.0 and the least value greater than
1.0 that is representable as a float. |
1.19209290E-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. |
2.2204460492503131E-16 |
|
FLT_MIN |
Minimum normalised positive
float. |
1.17549435E-38 |
|
DBL_MIN |
Minimum normalised positive
double. |
2.2250738585072016E-308 |
|
LDBL_MIN |
Minimum normalised positive long
double. |
2.2250738585072016E-308 |
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_ |
Maximum number of timer expiration overruns. |
32 |
32 |
|
FILESIZEBITS |
Minimum number of bits needed to represent as a signed
integer value the maximum size of a regular file. |
63 |
63 |
|
|
Maximum number of links to a single file. |
65535 |
65535 |
|
MQ_OPEN_ |
The maximum number of open message queue descriptors a
process may hold. |
No defined maximum
|
No defined maximum |
|
MQ_PRIO_ |
The maximum number of message priorities supported by the
implementation. |
No defined maximum |
No defined maximum |
|
NAME_ |
Maximum number of bytes in a filename (not including
terminating null). |
255 |
255 |
|
OPEN_ |
Maximum number of open files that one
process can have open at any one time. |
20 |
20 |
|
PAGESIZE |
Size of a page in bytes. |
4096 (PPC architecture) |
4096 (PPC architecture) |
|
PATH_ |
Maximum number of bytes in a pathname (including the
terminating null). |
1024 |
1024 |
|
PTHREAD_DESTRUCTOR_ITERATIONS |
Maximum number of attempts made to destroy a thread's
thread-specific data values on thread exit. |
4 |
4 |
|
PTHREAD_ |
Maximum number of data keys that can be created by a
process. |
256 |
256 |
|
PTHREAD_STACK_MIN |
Minimum size in bytes of thread stack
storage. |
4096 |
4096 |
|
PTHREAD_THREADS_ |
Maximum number of threads that can be created per process. |
No defined maximum |
No defined maximum |
|
RTSIG_ |
Maximum number of realtime
signals reserved for application use in this implementation. |
16 |
16 |
|
|
Maximum number of semaphores that a process may have. |
No defined maximum |
No defined maximum |
|
|
The maximum value a semaphore may have. |
32767 |
32767 |
|
SIGQUEUE_ |
Maximum number of queued signals that a process may send and
have pending at the receiver(s) at any time. |
32 |
32 |
|
SS_REPL_ |
The maximum number of replenishment operations that may be
simultaneously pending for a particular sporadic server scheduler. |
No defined maximum |
No defined maximum |
|
STREAM_ |
Number of streams that one process can
have open at one time. |
20 |
20 |
|
TIMER_ |
Maximum number of timers per process supported by the
implementation. |
No defined maximum |
No defined maximum |
|
TRACE_EVENT_NAME_ |
Maximum length of the trace event name. |
64 |
64 |
|
TRACE_NAME_ |
Maximum length of the trace generation version string or
of the trace stream name. |
8 |
8 |
|
TRACE_SYS_ |
Maximum number of trace streams that may simultaneously
exist in the system. |
No defined maximum |
No defined maximum |
|
TRACE_USER_EVENT_ |
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. |
256 |
256 |
|
TZNAME_ |
Maximum number of bytes supported for the name of a time
zone. |
6 |
6 |
Rationale
Each of these limits can vary within bounds set by the Base Definitions 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_
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 |
|
|
Maximum value of a char. |
255 |
|
|
Maximum value of an int. |
2147483647 |
|
LONG_ |
Maximum value of a long int. |
2147483647L |
|
LLONG_ |
Maximum value of a long long. |
9223372036854775807LL |
|
SHRT_ |
Maximum value of a short. |
32767 |
|
SSIZE_ |
Maximum value of an object of type ssize_t. |
2147483647 |
|
UINT_ |
Maximum value of an unsigned int. |
4294967295 |
|
ULONG_ |
Maximum value of an unsigned long int. |
4294967295 |
|
ULLONG_ |
Maximum value of a unigsned
long long. |
18446744073709551615ULL |
|
USHRT_ |
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_ |
Maximum size in bytes of the longest filename string that
the implementation guarantees can be opened. |
256 |
|
FOPEN_ |
Number of streams which the implementation guarantees can
be open simultaneously. |
20 |
|
L_tmpnam |
Maximum size of character array to hold tmpnam()
output. |
16 |
|
|
Minimum number of unique filenames generated by tmpnam(),
which is the maximum number of times an application can call tmpnam() reliably. |
32 |
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 |
No |
|
ENAMETOOLONG |
Yes |
|
|
ETXTBSY |
No |
|
|
chdir() |
ENAMETOOLONG |
Yes |
|
ELOOP |
No |
|
|
clock_settime() |
EPERM |
Yes |
|
close() |
EIO |
Yes |
|
closedir() |
EBADF |
Yes |
|
EINTR |
No |
|
|
erfc() * |
Range Error |
No |
|
exp() * |
Range Error |
Yes |
|
exp2() * |
Range Error |
Yes |
|
expm1() * |
Range Error |
Yes |
|
fchdir() |
EINTR |
No |
|
EIO |
No |
|
|
fclose() |
ENXIO |
No |
|
fcntl() |
EDEADLK |
Yes |
|
fdim() * |
Range Error |
No |
|
fdopen() |
EBADF |
Yes |
|
EINVAL |
No |
|
|
EMFILE |
Yes |
|
|
ENOMEM |
Yes |
|
|
fflush() |
ENXIO |
No |
|
fgetc() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
fgetpos() |
EBADF |
Yes |
|
ESPIPE |
No |
|
|
fgetwc() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
fileno() |
EBADF |
No |
|
fmod() * |
Range Error |
Yes |
|
fopen() |
EINVAL |
Yes |
|
ELOOP |
No |
|
|
EMFILE |
Yes |
|
|
ENAMETOOLONG |
Yes |
|
|
ENOMEN |
Yes |
|
|
ETXTBSY |
No |
|
|
fpathconf() |
EBADF |
Yes |
|
EINVAL |
Yes |
|
|
fputc() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
fread() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
freopen() |
EINVAL |
Yes |
|
ELOOP |
No |
|
|
ENAMETOOLONG |
Yes |
|
|
ENOMEM |
Yes |
|
|
ENXIO |
No |
|
|
ETXTBSY |
No |
|
|
fscanf() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
fstat() |
EOVERFLOW |
No |
|
ftell() |
ESPIPE |
No |
|
getcwd() |
EACCES |
No |
|
ENOMEM |
No |
|
|
ldexp() * |
Range Error |
Yes |
|
link() |
ELOOP |
No |
|
ENAMETOOLONG |
Yes |
|
|
mkdir() |
ELOOP |
No |
|
ENAMETOOLONG |
Yes |
|
|
mktime() |
EOVERFLOW |
No |
|
mlock() |
EINVAL |
No |
|
ENOMEM |
Yes |
|
|
munlock() |
EINVAL |
No |
|
mlockall() |
ENOMEM |
No |
|
ENOPERM |
No |
|
|
mq_getattr() |
EBADF |
Yes |
|
mq_receive() |
EBADF |
Yes |
|
mq_timedreceive() |
EBADF |
Yes |
|
open() |
EAGAIN |
Yes |
|
EINVAL |
Yes |
|
|
ELOOP |
No |
|
|
ENAMETOOLONG |
Yes |
|
|
ETXTBSY |
No |
|
|
opendir() |
ELOOP |
No |
|
EMFILE |
Yes |
|
|
ENAMETOOLONG |
Yes |
|
|
ENFILE |
Yes |
|
|
pathconf() |
EACCES |
Yes |
|
EINVAL |
Yes |
|
|
ELOOP |
No |
|
|
ENAMETOOLONG |
Yes |
|
|
ENOENT |
Yes |
|
|
ENOTDIR |
No |
|
|
posix_trace_attr_destroy() |
EINVAL |
Yes |
|
posix_trace_attr_getclockres() |
EINVAL |
Yes |
|
posix_trace_attr_getcreatetime() |
EINVAL |
Yes |
|
posix_trace_attr_getgenversion() |
EINVAL |
Yes |
|
posix_trace_attr_getname() |
EINVAL |
Yes |
|
posix_trace_attr_getinherited() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
posix_trace_attr_getlogfullpolicy() |
EINVAL |
Yes |
|
posix_trace_attr_getstreamfullpolicy() |
EINVAL |
Yes |
|
posix_trace_attr_setinherited() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
posix_trace_attr_setlogfullpolicy() |
EINVAL |
Yes |
|
posix_trace_attr_setstreamfullpolicy() |
EINVAL |
Yes |
|
posix_trace_attr_getlogsize() |
EINVAL |
Yes |
|
posix_trace_attr_getmaxdatasize() |
EINVAL |
Yes |
|
posix_trace_attr_getmaxsystemeventsize() |
EINVAL |
Yes |
|
posix_trace_attr_getmaxusereventsize() |
EINVAL |
Yes |
|
posix_trace_attr_getstreamsize() |
EINVAL |
Yes |
|
posix_trace_attr_setlogsize() |
EINVAL |
Yes |
|
posix_trace_attr_setstreamsize() |
EINVAL |
Yes |
|
posix_trace_close() |
EINVAL |
Yes |
|
posix_trace_rewind() |
EINVAL |
Yes |
|
posix_trace_eventset_add() |
EINVAL |
Yes |
|
posix_trace_eventset_del() |
EINVAL |
Yes |
|
posix_trace_eventset_empty() |
EINVAL |
Yes |
|
posix_trace_eventset_fill() |
EINVAL |
Yes |
|
posix_trace_eventset_ismember() |
EINVAL |
Yes |
|
pow() * |
Range Error |
Yes |
|
pthread_attr_destroy() |
EINVAL |
Yes |
|
pthread_attr_init() |
EBUSY |
No |
|
pthread_attr_getdetachstate() |
EINVAL |
Yes |
|
pthread_attr_setdetachstate() |
EINVAL |
Yes |
|
pthread_attr_getguardsize() |
EINVAL |
Yes |
|
pthread_attr_setguardsize() |
EINVAL |
Yes |
|
pthread_attr_getinheritsched() |
EINVAL |
Yes |
|
pthread_attr_setinheritsched() |
EINVAL |
Yes |
|
ENOSUP |
No |
|
|
pthread_attr_getschedparam() |
EINVAL |
Yes |
|
pthread_attr_setschedparam() |
EINVAL |
Yes |
|
ENOSUP |
No |
|
|
pthread_attr_getschedpolicy() |
EINVAL |
Yes |
|
pthread_attr_setschedpolicy() |
EINVAL |
Yes |
|
ENOSUP |
Yes |
|
|
pthread_attr_getscope() |
EINVAL |
Yes |
|
pthread_attr_setscope() |
EINVAL |
Yes |
|
ENOSUP |
Yes |
|
|
pthread_attr_getstack() |
EINVAL |
Yes |
|
pthread_attr_setstack() |
EINVAL |
Yes |
|
EBUSY |
No |
|
|
pthread_attr_getstackaddr() |
EINVAL |
Yes |
|
pthread_attr_setstackaddr() |
EINVAL |
Yes |
|
pthread_attr_getstacksize() |
EINVAL |
Yes |
|
pthread_attr_setstacksize() |
EINVAL |
Yes |
|
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 |
No |
|
EINVAL |
Yes |
|
|
pthread_cond_timedwait() |
EINVAL |
Yes |
|
EPERM |
Yes |
|
|
pthread_cond_wait() |
EINVAL |
Yes |
|
EPERM |
Yes |
|
|
pthread_condattr_destroy() |
EINVAL |
Yes |
|
pthread_condattr_getclock() |
EINVAL |
Yes |
|
pthread_condattr_setclock() |
EINVAL |
Yes |
|
pthread_condattr_getpshared() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
pthread_condattr_setpshared() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
pthread_create() |
EINVAL |
Yes |
|
pthread_detach() |
EINVAL |
Yes |
|
ESRCH |
Yes |
|
|
pthread_getcpuclockid() |
ESRCH |
Yes |
|
pthread_getschedparam() |
ESRCH |
Yes |
|
pthread_setschedparam() |
EINVAL |
Yes |
|
ENOTSUP |
No |
|
|
EPERM |
No |
|
|
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 |
No |
|
EINVAL |
Yes |
|
|
pthread_mutex_lock() |
EINVAL |
Yes |
|
EDEADLK |
No |
|
|
pthread_mutex_trylock() |
EINVAL |
Yes |
|
pthread_mutex_unlock() |
EINVAL |
Yes |
|
EPERM |
Yes |
|
|
pthread_mutex_timedlock() |
EINVAL |
Yes |
|
EDEADLK |
No |
|
|
pthread_mutexattr_destroy() |
EINVAL |
Yes |
|
pthread_mutexattr_getprioceiling() |
EINVAL |
Yes |
|
EPERM |
No |
|
|
pthread_mutexattr_setprioceiling() |
EINVAL |
Yes |
|
EPERM |
No |
|
|
pthread_mutexattr_getprotocol() |
EINVAL |
Yes |
|
EPERM |
No |
|
|
pthread_mutexattr_setprotocol() |
EINVAL |
Yes |
|
EPERM |
No |
|
|
pthread_mutexattr_getpshared() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
pthread_mutexattr_setpshared() |
EINVAL |
UNSUPPORTED (Not PSE52) |
|
pthread_mutexattr_gettype() |
EINVAL |
Yes |
|
pthread_mutexattr_settype() |
EINVAL |
Yes |
|
pthread_once() |
EINVAL |
Yes |
|
pthread_setcancelstate() |
EINVAL |
Yes |
|
pthread_setcanceltype() |
EINVAL |
Yes |
|
pthread_schedprio() |
EINVAL |
Yes |
|
ENOTSUP |
No |
|
|
EPERM |
No |
|
|
ESRCH |
Yes |
|
|
putc() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
putchar() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
puts() |
ENOMEM |
Yes |
|
ENXIO |
No |
|
|
read() |
EIO |
Yes |
|
ENOBUFS |
No |
|
|
ENOMEM |
No |
|
|
ENXIO |
No |
|
|
readdir() |
EBADF |
Yes |
|
ENOENT |
Yes |
|
|
remove() |
EBUSY |
Yes |
|
ELOOP |
No |
|
|
ENAMETOOLONG |
Yes |
|
|
ETXTBSY |
No |
|
|
rename() |
ELOOP |
No |
|
ENAMETOOLONG |
Yes |
|
|
ETXTBSY |
Yes |
|
|
rmdir() |
ELOOP |
No |
|
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 |
No |
|
|
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 |
Yes |
|
sigwaitinfo() |
EINVAL |
Yes |
|
stat() |
ELOOP |
No |
|
ENAMETOOLONG |
Yes |
|
|
EOVERFLOW |
No |
|
|
strcoll() |
EINVAL |
No |
|
strerror() |
EINVAL |
No |
|
strerror_r() |
ERANGE |
No |
|
strtod() |
EINVAL |
No |
|
strtoimax() |
EINVAL |
No |
|
strtol() |
EINVAL |
No |
|
strtoul() |
EINVAL |
No |
|
strtoumax() |
EINVAL |
No |
|
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 |
No |
|
ENAMETOOLONG |
Yes |
|
|
ETXTBSY |
No |
|
|
utime() |
ELOOP |
No |
|
ENAMETOOLONG |
Yes |
|
|
vfscanf() |
EILSEQ |
Yes |
|
EINVAL |
No |
|
|
ENOMEM |
Yes |
|
|
ENXIO |
No |
|
|
write() |
ENETDOWN |
No |
|
ENETUNREACH |
No |
|
|
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. |
|
|
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
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. |
|
|
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: |
|
|
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 |
|
|
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 |
No |
|
The implementation provides a C-language compilation
environment with |
Yes |
|
The implementation provides a C-language compilation
environment with |
No |
|
The implementation provides a C-language compilation
environment with |
Yes |
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 |
No |
|
The implementation provides an execution environment with |
Yes |
|
The implementation provides an execution environment with |
No |
|
The implementation provides an execution environment with |
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).
|
The POSIX tests must be executed against a
standardized target configuration. The target must have support for, among
other things, a VxWorks ROMFS file system and a |
|
|
|
Date |
Name |
Comment |
|
New |
|
|
|
|
|
|
|
|
|
|
Version 1.01
Copyright © 1998-2006 The
Open Group. All Rights Reserved. The
Open Group and Boundaryless Information Flow are
trademarks and UNIX is a registered trademark of The Open Group in the