Draft POSIX Conformance Template for Austin-294r1 Page 1 of 1 the 1003.13, 2003 Edition PSE52 Submitted by Andrew Josey, The Open Group. November 2 2006 Note to users of this template: Please remove the above header from any document produced from this and replace with an appropriate title section as note in the first paragraph below. IEEE Std 1003.13-2003 states "(1) If the implementation is fully conformant to the referenced base standard(s), then that implementation may cite the separate conformance documents that document the base standard conformance. This will primarily apply to implementations that support the PSE53 or PSE54 Profiles." The conformance document for this profile shall contain a statement that indicates the full name, number, and date of the standard (i.e., the profile standard) that applies. The text below provides a sample template for PSE52 based on the PCD for 1003.1-2001 that you should complete. If the implementation supports functionality associated with options not listed below then the PCD should include appropriate documentation (see the Austin Group document register for examples of PCDs for the larger profiles). POSIX Conformance Document Requirements (derived from XBD 2.1.2) The conformance document shall have the same structure as IEEE Std 1003.1-2001, with the information presented in the appropriate sections and subsections. Sections and subsections that consist solely of subordinate section titles, with no other information, are not required. The conformance document shall not contain information about extended facilities or capabilities outside the scope of IEEE Std 1003.1-2001. The conformance document shall contain a statement that indicates the full name, number, and date of the standard that applies. The conformance document may also list international software standards that are available for use by a Conforming POSIX Application. Applicable characteristics where documentation is required by one of these standards, or by standards of government bodies, may also be included. The conformance document shall describe the limit values found in the headers and , stating values, the conditions under which those values may change, and the limits of such variations, if any. The conformance document shall describe the behavior of the implementation for all implementation-defined features defined in IEEE Std 1003.1-2001. This requirement shall be met by listing these features and providing either a specific reference to the system documentation or providing full syntax and semantics of these features. When the value or behavior in the implementation is designed to be variable or customized on each instantiation of the system, the implementation provider shall document the nature and permissible ranges of this variation. The conformance document may specify the behavior of the implementation for those features where IEEE Std 1003.1-2001 states that implementations may vary or where features are identified as undefined or unspecified. The conformance document shall not contain documentation other than that specified in the preceding paragraphs except where such documentation is specifically allowed or required by other provisions of IEEE Std 1003.1-2001. The phrases "shall document" or "shall be documented" in IEEE Std 1003.1-2001 mean that documentation of the feature shall appear in the conformance document, as described previously, unless there is an explicit reference in the conformance document to show where the information can be found in the system documentation. The system documentation should also contain the information found in the conformance document. Base Definitions 3. Definitions 3.4 Additional File Access Control Mechanism The PCD shall document whether, and if so, how additional file access control mechanisms are supported. 3.12 Alternate File Access Control Mechanism The PCD shall document whether, and if so, how additional file alternate control mechanisms are supported. 3.19 Appropriate Privileges The PCD shall document how appropriate privileges are supported. 3.97 Clock Tick The PCD shall document the number of clock ticks that occur each second. 3.159 Extended Security Controls The PCD shall document additional security controls, if any, allowed by the file access permission and appropriate privilege mechanisms through which the system supports different security policies to those described in IEEE Std 1003.1-2001. 3.387 System Trace Event If the TRC option is supported: The PCD shall document the name of system trace events beyond those specified in IEEE Std 1003.1-2001. The PCD shall document the content and length of data for system trace events beyond those specified in IEEE Std 1003.1-2001. 3.409 Trace Generation Version If the TRC option is supported, the PCD shall describe the characteristics of the Trace Generation Version data object generated by the trace system that describes the origin and version of the trace system. 4. General Concepts 4.3 Extended Security Controls The PCD shall document any extended security controls supported by the implementation. 4.9 Measurement of Execution Time The PCD shall document the mechanism used to measure execution time and shall also define to whom the CPU time that is consumed by interrupt handlers and system services on behalf of the operating system will be charged. 4.11 Pathname Resolution The PCD shall document the interpretation of a pathname that begins with two successive slashes. 4.14 Seconds Since the Epoch The PCD shall document how any changes are made to the value of seconds since the Epoch to align to a desired relationship with the current actual time. 4.17 Tracing If the TRC option is supported, the PCD shall document the actions associated with a trace point, if any. 4.18 Treatment of Error Conditions for Mathematical Functions 4.18.1 Domain Error The PCD shall document the return value for a domain error. 4.18.3 Range Error 4.18.3.2 Result Underflows The PCD shall document the return value for a result that underflows. The PCD shall document whether errno is set to [ERANGE] when the integer expression (math_errhandling & MATH_ERRNO) is non-zero. The PCD shall document whether the ``underflow'' floating-point exception is raised when the integer expression (math_errhandling & MATH_ERREXCEPT) is non-zero. 5. File Format Notation 6. Character Set 6.4 Character Set Description File The PCD shall document whether or not users or applications can provide additional character set description files. The PCD shall document the manner in which decimal, octal and hexidecimal constants are represented in the character stored in the system. 7. Locale 7.1 General The PCD shall document the mechanism used to locate a locale when the value of a locale environment variable does not begin with a slash. 7.2 POSIX Locale The PCD shall the document the implementation's default locale to be invoked when no locale environment variables are set, or they are set to the empty string. 7.3 Locale Definition The PCD shall document whether the implementation supports additional locale categories beyond those specified in the standard. The PCD shall document the values of the characters in the portable character set. 8. Environment Variables 8.2 Internationalization Variables The PCD shall document additional semantics, if any, for the LC_COLLATE environment variable. The PCD shall document additional semantics, if any, for the LC_CTYPE environment variable. The PCD shall document additional semantics, if any, for the LC_MESSAGES environment variable. The PCD shall document additional semantics, if any, for the LC_MONETARY environment variable. The PCD shall document additional semantics, if any, for the LC_NUMERIC environment variable. The PCD shall document additional semantics, if any, for the LC_TIME environment variable. The PCD shall document which default locale shall be used in the case that all of the following are true: 1. the LC_ALL variable is not defined, and 2. the LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, and LC_TIME variables are not defined, and 3. the LANG variable is not defined or is set to the empty string. The PCD shall document additional criteria, if any, for determining valid locales. 8.3 Other Environment Variables The PCD shall document in the case when the first character of the TZ variable is a colon, how the following characters are handled. 13. Headers The PCD shall document the default state (on or off) for the FENV_ACCESS pragma. The PCD shall document the accuracy of the floating-point operations ('+', '-', '*', '/') and of the library functions in and that return floating-point results. The PCD shall document the rounding mode for floating-point addition, including documenting any additional values beyond those specified. The PCD shall document the evaluation format mode for operations with floating operands and values including documenting any additional values beyond those specified. The PCD shall document the values of FLT_RADIX, FLT_MANT_DIG, DBL_MANT_DIG, LDBL_MANT_DIG, DECIMAL_DIG, FLT_DIG, DBL_DIG, LDBL_DIG, FLT_MIN_EXP, DBL_MIN_EXP, LDBL_MIN_EXP, FLT_MIN_10_EXP, DBL_MIN_10_EXP, LDBL_MIN_10_EXP, FLT_MAX_EXP, DBL_MAX_EXP, LDBL_MAX_EXP, FLT_MAX_10_EXP, DBL_MAX_10_EXP, LDBL_MAX_10_EXP, FLT_MAX, DBL_MAX, LDBL_MAX, FLT_EPSILON, DBL_EPSILON, LDBL_EPSILON, FLT_MIN, DBL_MIN, LDBL_MIN The PCD shall describe the limit values found in the headers , stating values, the conditions under which those values may change, and the limits of such variations, if any. The PCD shall document the type definitions for float_t and double_t for values of FLT_EVAL_METHOD other than 0,1 or 2. The PCD shall document additional macros for floating-point classifications, if any. They shall begin with the prefix FP_ and an uppercase letter. The PCD shall document the default state (on or off) for the FP_CONTRACT pragma. The PCD shall document whether realtime signal behavior is supported for other signals outside of the range SIGRTMIN through SIGRTMAX The PCD shall document additional signals, if any, beyond those specified. The PCD shall document the values for the limits of specified-width integer types. The PCD shall document the values of the following macros: PTRDIFF_MIN, PTRDIFF_MAX, SIG_ATOMIC_MIN, SIG_ATOMIC_MAX, SIZE_MAX The PCD shall document other file mode bits, if any, that can be OR'd into S_IRWXU, S_IRWXG, and S_IRWXO. If the MON option is supported the PCD shall document the maximum possible clock jump for the system-wide monotonic clock. System Interfaces 2.3 Error Numbers (1114) The PCD shall document additional error numbers over those specified in IEEE Std 1003.1-2001 Section 2.3, if any, that are defined when the header is #included. 2.4 Signal Concepts (1155) The PCD shall document whether a signal is delivered or accepted more than once, for the case when a subsequent occurrence of a pending signal is generated. (1166) The PCD shall document any conditions beyond those specified in the System Interfaces Volume of IEEE Std 1003.1-2001 in which the implementation generates signals. 2.4.2 Realtime Signal Generation and Delivery (1231) If the RTS option is supported the PCD shall document the signal mask for threads created that use the alternate event notification (sigev_notify_function). 2.4.3 Signal Actions (1314) If the RTS option is supported if a signal is generated by functions or events other than those specified in this section, the PCD shall document si_code value set for the corresponding event or function. 2.5 Standard I/O Streams (1392) The PCD shall document whether the file position indicator is initially positioned at the beginning or end of the file when a file is opened with append mode. (1404) The PCD shall document whether the system supports the characteristics for unbuffered and fully buffered streams, and the affects, if any of setbuf() and setvbuf(). 2.5.1. Interaction of File Descriptors and Standard I/O Streams (1489) The PCD shall document whether and under what conditions all input is seen exactly once. 2.8 Realtime 2.8.3 Memory Management (1765) If the ML or MLR options are supported the PCD shall document whether locking memory guarantees fixed translation between virtual addresses (as seen by the process) and physical addresses. 2.8.4 Processing Sheduling If the PS option is supported: (1851) The PCD shall document any other scheduling policies beyond those specified. (1941) If the SS or TSP options are supported The PCD shall document the resolution of the execution time clock for the scheduling policies supported. (1984) The PCD shall document the effect of scheduling threads with the SCHED_OTHER policy when other threads are executing under SCHED_FIFO, SCHED_RR or (if the SS option is supported) SCHED_SPORADIC. 2.8.5 Clocks and Timers (2034) If the MON option is supported the PCD shall document the The maximum possible clock jump for the system-wide monotonic clock. (2041) If the actual resolution supported for a time service based on one of the supported clocks differs from the resolution supported for that clock, then the PCD shall document this difference. 2.9.4 Thread Scheduling If the TPS option is supported: (2161) The PCD shall document the default scheduling contention scope, and the default values of other scheduling attributes. (2176) The PCD shall document how the system scheduling attributes of a thread created with PTHREAD_SCOPE_PROCESS scheduling contention scope map to the system attribute space of the scheduling attributes with which the thread was created. (2200) The PCD shall document how the system determines its choice of scheduling allocation domain size, and describe the level of application control over scheduling allocation domains. (2211) The PCD shall document for application threads with scheduling allocation domains of size greater than one, how the rules defined for SCHED_FIFO, SCHED_RR, and SCHED_SPORADIC are used. (2212) The PCD shall document the manner in which each thread with system scheduling contention scope competes for the processors in its scheduling allocation domain according to its priority. (2216) If the TSP option is supported The PCD shall document how the rules defined for SCHED_SPORADIC in Scheduling Policies (on page 44) are used for application threads whose scheduling allocation domain size is greater than one. (2219) The PCD shall document any scheduling policies beyond SCHED_OTHER, SCHED_FIFO, SCHED_RR, and SCHED_SPORADIC, as well as the effects of the scheduling policies indicated by these other values, and the attributes required in order to support such a policy. Furthermore, the implementation shall document the effect of all processor scheduling allocation domain values supported for these policies. 2.11 Tracing If the TRC option is supported: 2.11.1 Tracing Definitions (3079) The PCD shall document the characteristics of system trace events. (3100) The PCD shall document the clock used for the posix_timestamp member (the time at which the trace event was generated ). 2.11.2 Trace Event Type Definitions (3153) The PCD shall document any system specific trace error conditions. (3166) The PCD shall document conditions that can generate a POSIX_TRACE_ERROR trace event. ------ XSH Chapter 3 acos,acosf,acosl The PCD shall document the return value for the case of finite values of x not in the range [-1,1]. If the MX option is supported the PCD shall document the return value for the case when x is +/-Inf. acosh,acoshf,acoshl The PCD shall document the return value for the case of finite values of x < 1 If the MX option is supported the PCD shall document the return value for the case when x is -Inf. asin,asinf,asinl The PCD shall document the return value for the case of finite values of x not in the range [-1,1] If the MX option is supported the PCD shall document the return value for the case when x is +/-Inf. atanh,atanhf,atanhl The PCD shall document the return value for the case of finite values of |x| > 1 If the MX option is supported the PCD shall document the return value for the case when x is +/-Inf. calloc The PCD shall document the behavior of calloc() when the size of space requested is zero as either being a null pointer or a unique pointer. clock_getres If the TMR option is supported The PCD shall document the resolution of the supported clocks. The PCD shall document the effect of setting a clock via clock_settime( ) on armed per-process timers associated with a clock other than CLOCK_REALTIME. The PCD shall document the appropriate privileges required to set a particular clock. cos,cosf,cosl If the MX option is supported the PCD shall document the return value for the case when x is +/-Inf. erfc,erfcf,erfcl The PCD shall document the return value for the case of a correct value that would cause underflow and is not representable. exp,expf,expl The PCD shall document the return value for the case when the correct value would cause underflow and is not representable. exp2,exp2f,exp2l The PCD shall document the return value for the case when the correct value would cause underflow and is not representable. fclose The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. fcntl The PCD shall document additional values for /cmd/ defined in . Their names shall start with F_. fdim,fdimf,fdiml The PCD shall document the return value for the case when x-y is positive and underflows fegetexecptflag The PCD shall document the representation of the states of the floating-point status flags. feraiseexcept The PCD shall document whether the feraiseexcept( ) function additionally raises the inexact floating-point exception whenever it raises the overflow or underflow floating-point exception. fflush The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. fgetc The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. fma,fmaf,fmal If the MX option is supported: The PCD shall document the return value for the case when x multiplied by y is an exact infinity and z is also an infinity but with the opposite sign The PCD shall document the return value for the case when one of x and y is infinite, the other is zero, and z is not a NaN an infinity but with the opposite sign fmod,fmodf,fmodl The PCD shall document the return value for the case when the correct value would cause underflow and is not representable. If the MX option is supported, the PCD shall document the return value for the case when y is zero. If the MX option is supported, the PCD shall document the return value for the case when x is infinite. fpclassify The PCD shall document additional classification categories, if any, beyond Nan, infinite, normal, subnormal and zero. fprintf The PCD shall document the low-order digit rounding for numbers in double format. The PCD shall document whether the style for representing double argument infinity values for the f conversion specifier is "[-]inf" or "[-]infinity". The PCD shall document whether the style for representing double argument infinity values for the F conversion specifier is "[-]INF" or "[-]INFINITY". The PCD shall document whether the style for representing double argument NaN values for the f conversion specifier is "[-]nan(/n-char-sequence/)" or "[-]nan". If the form is "[-]nan(/n-char-sequence/)" the PCD shall document the meaning of /n-char-sequence/. The PCD shall document whether the style for representing double argument NaN values for the F conversion specifier is "[-]NAN(/n-char-sequence/)" or "[-]NAN". If the form is "[-]NAN(/n-char-sequence/)" the PCD shall document the meaning of /n-char-sequence/. The PCD shall document the manner in which the value of a pointer is converted to a sequence of printable character for the p conversion specifier. fputc The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. freopen The PCD shall document the permitted changes of mode, if any, and under what circumstances. fscanf The PCD shall document the behavior when a '-' is in the scanlist and is not the first character, nor the second where the first character is a '^', nor the last character. The PCD shall document the set of sequences that are matched by the p conversion specifier. This shall correspond to the same set of sequences produced by the %p conversion specification of the corresponding fprintf() functions. The PCD shall document the interpretation of the input item for the p conversion specifier. fseek The PCD shall document the behavior of fseek() on devices which are incapable of seeking. The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. fsetpos The PCD shall document the behavior of fsetpos() on devices which are incapable of seeking. The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. fstat The PCD shall document, for implementations that provide additional or alternative file access control mechanisms, any conditions that cause fstat() to fail beyond those specified in IEEE Std 1003.1-2001. fsync The PCD shall document the manner in which data is transferred to the storage device when an fsync() call occurs. kill For implementations that provide extended security controls, the PCD shall document further implementation-defined restrictions on the sending of signals, including the null signal, if any. ldexp,ldexpf,ldexpl The PCD shall document the return value for the case when the correct value would cause underflow and is not representable. log,logf,logl The PCD shall document the return value for the case when the finite values of x are less than zero. If the MX option is supported, the PCD shall document the return value for the case when the x is -Inf. log10,log10f,log10l The PCD shall document the return value for the case when the finite values of x are less than zero. If the MX option is supported, the PCD shall document the return value for the case when the x is -Inf. log1p,log1pf,log1pl The PCD shall document the return value for the case when the finite values of x are less than -1. If the MX option is supported, the PCD shall document the return value for the case when the x is -Inf. log2,log2f,log2l The PCD shall document the return value for the case when the finite values of x are less than 0. If the MX option is supported, the PCD shall document the return value for the case when the x is -Inf. lseek The PCD shall document the behavior of lseek() on devices which are incapable of seeking. malloc The PCD shall document the behavior of malloc() when the size of space requested is zero as either being a null pointer or a unique pointer. mkdir The PCD shall document the meaning of additional bits other than the file permission bits being set in the mode argument to mkdir(). mlock If the MLR option is supported, the PCD shall document the limit on the amount of memory that the process may lock. mlockall,munlockall If the ML option is supported, the PCD shall document the behavior when MCL_FUTURE is specified, and the automatic locking of future mappings eventually causes the amount of locked memory to exceed the amount of available physical memory or another limit. In addition the PCD shall document the manner in which the implementation informs the application of these situations. If the ML option is supported, the PCD shall document the limit on the amount of memory that the process may lock. mmap If the MF or SHM or TYM options are supported: The PCD shall document the return value for the mmap() function. The PCD shall document whether MAP_FIXED is supported. The PCD shall document how the implementation uses /addr/ to arrive at /pa/ when MAP_FIXED is not set. If there are limits on the number of memory regions that can be mapped then the PCD shall document them. mq_open If the MSG option is supported: The PCD shall document the effect of calling mq_open when the name argument does not begin with a slash character. The PCD shall document the interpretation of the name argument when it contains additional slash characters other than the leading slash character. The PCD shall document the effect when bits in mode other than file permission bits are set The PCD shall document the default message queue attributes for a created message queue when mq_open is called with attr set to NULL. mq_receive If the MSG option is supported: The PCD shall document the result if the value of msg_len is greater than {SSIZE_MAX}. mq_setattr If the MSG option is supported: The PCD shall document whether any implementation flags are OR'd with O_NONBLOCK for the mq_flags member. open The PCD shall document the effect of the O_TRUNC flag for file types other than regular files. posix_trace_attr_getlogsize If the TRC option is supported: If the TRL option is supported, the PCD shall document the default value for the log-max-size attribute. posix_trace_attr_getmaxdatasize If the TRC option is supported: The PCD shall document the default value for the max-data-size attribute. posix_trace_attr_getlogstreamsize If the TRC option is supported: The PCD shall document the default value for the stream-min-size attribute. posix_trace_create_withlog If the TRC option is supported: If the TRL option is supported, the PCD shall document the list of the appropriate file types that are compatible with each log policy for the log-max-size attribute. posix_trace_flush,posix_trace_shutdown If the TRC option is supported, the PCD shall document the maximum file size of the trace log file. posix_trace_eventset If the TRC and TEF options are supported, the PCD shall include a description of all the process-independent implementation-defined system trace event types. If the TRC and TEF options are supported, the PCD shall include a description of all implementation-defined system trace event types. posix_trace_getnext_event,posix_trace_trygetnext_event posix_trace_timedgetnext_event If the TRC option is supported, the PCD shall document the time resolution that causes the ordering of trace events occurring very close to each other to be unknown. pow,powf,powl The PCD shall document the return value for the case when the finite values of x are less than 0 and finite non-integer values of y The PCD shall document the return value for the case when the correct value would cause underflow and is not representable pthread_attr_destroy If the THR option is supported, and the implementation of the pthread_attr_destroy sets attr to an invalid value, the PCD shall document the value used. pthread_condattr_destroy If the THR option is supported if the implementation supports condition variable attributes not defined by IEEE Std 1003.1-2001, their default values, and the names of the associated functions to get and set those attribute values shall be documented in the PCD. pthread_getschedparam,pthread_setschedparam If the THR and TPS options are supported the PCD shall document the affected scheduling parameters when the scheduling policy is SCHED_OTHER. If the TSP option is supported, the PCD shall document whether the pthread_setschedparam( ) function is supported if the scheduling policy was not SCHED_SPORADIC at the time of the call. pthread_rwlock_rdlock If the THR option is supported and the TPS option is not supported, the PCD shall document whether the calling thread acquires the lock when a writer does not hold the lock and there are writers blocked on the lock. If the THR option is supported the PCD shall document the maximum number of simultaneous read locks that an implementation guarantees can be applied to a read-write lock. pthread_rwlock_unlock If the THR option is supported and the TPS option is not supported the PCD shall document whether write locks take precedence over read locks. pthread_rwlockattr_getpshared If the THR option is supported if the implementation supports read-write lock attributes not defined by IEEE Std 1003.1-2001, their default values, and the names of the associated functions to get and set those attribute values shall be documented in the PCD. read For special device files, the PCD shall document the result of subsequent read( ) requests after the end-of-file condition has been reached. The PCD shall document the result of a read() call when the value of nbyte is greater than {SSIZE_MAX}. The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned. remainder,remainderf,remainderl If the MX option is supported, the PCD shall document the return value in the case when x is infinite or y is zero and the other is non-NaN. remquo,remquof,remquol The PCD shall document the value n used to determine the magnitude of the result. The value n shall be an integer greater than or equal to 3. If the MX option is supported, the PCD shall document the return value for the case when x is +/-Inf or y is zero and the other argument is non-zero. rint,rintf,rintl The PCD shall document how the current rounding mode is determined. scalbln,scalblnf,scalblnl,scalbn,scalbnf,scalbnl The PCD shall document the return value when the correct value would cause underflow and is not representable sem_open If the SEM option is supported: The PCD shall document the effect of calling sem_open when the name argument does not begin with a slash character. The PCD shall document the interpretation of the name argument when it contains additional slash characters other than the leading slash character. setlocale The PCD shall document the valid strings for the locale argument. The PCD shall document the default native environment when the locale string is set to "". shm_open If the SHM option is supported: The PCD shall document the effect of calling shm_open when the name argument does not begin with a slash character. The PCD shall document the interpretation of the name argument when it contains additional slash characters other than the leading slash character. sigaction The PCD shall document the disposition of subsequent occurrences of sig when it is already pending, when SA_SIGINFO is not set in sa_flags. signal The PCD shall document whether when a signal occurs and func points to a function, the equivalent of signal(sig,SIG_DFL) is executed or if the the implementation prevents some set of signals (at least including sig) from occurring until the current signal handling has completed. If the latter then the PCD shall document the set of signals. The PCD shall document values other than SIGFPE, SIGILL or SIGSEGV that correspond to a computational exception. sigwait The PCD shall document in the case when prior to a call to sigwait( ) there are multiple pending instances of a single signal number, whether upon successful return there are any remaining pending signals for that signal number. sin,sinf,sinl If the MX option is supported, the PCD shall document the return value for the case when x is +/-Inf. sqrt,sqrtf,sqrtl The PCD shall document the return value for the case of finite values of x < -0. If the MX option is supported the PCD shall document the return value for the case when x is -Inf. stat The PCD shall document, for implementations that provide additional or alternative file access control mechanisms, any conditions that cause stat() to fail beyond those specified in IEEE Std 1003.1-2001. strtod,strtof,strtol The PCD shall document the meaning of the n-char sequences. If other subject sequences beyond those specified are accepted in other locales than the C or POSIX locale, the PCD shall document them. strtol,stroll If other subject sequences beyond those specified are accepted in other locales than the C or POSIX locale, the PCD shall document them. strtoul,stroull If other subject sequences beyond those specified are accepted in other locales than the C or POSIX locale, the PCD shall document them. tan,tanf,tanl The PCD shall document the return value in the case when the correct value would cause underflow and is not representable. If the MX option is supported, the PCD shall document the return value for the case when x is +/-Inf. tgamma,tgammaf,tgammal The PCD shall document the return value for the case when x is a negative integer. If the MX option is supported, the PCD shall document the return value for the case when x is -Inf. timer_create If the TMR option is supported, the PCD shall document whether a timer_create( ) function will succeed if the value defined by clock_id corresponds to the CPU-time clock of a process or thread different from the process or thread invoking the function. tmpnam The PCD shall document the behavior if the function is called more than {TMP_MAX} times in a single process. tzset The PCD shall document the default timezone information used by the system if the TZ environment variable is not set. uname The PCD shall document the communications network for this node. The PCD shall document the format of each member of the utsname structure. write The PCD shall document the result of a write() call when the value of nbyte is greater than {SSIZE_MAX}. The PCD shall document any additional circumstances to those specified for an [EIO] error to be returned.