Document Number: AUSTIN/138 Title: XSH/ft/5 Aardvark Change Request Report (draft) Revision Date: 2002-09-06 Source: Andrew Josey, Chair Action: for review This report contains the draft dispositions of the aardvark comments submitted against the XSH/ft/5 (5th batch of FT aardvark - post TC1 cutoff) text. Aardvark Summary Table ______________________ ERN 1 Accept ERN 2 Accept ERN 3 Accept ERN 4 OPEN _____________________________________________________________________________ EDITORIAL Enhancement Request Number 1 gwc@opengroup.org fmin (rdvk# 2) [gwc fmax NaN] Thu, 22 Aug 2002 16:34:28 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 379 Line: 12225-12231 Section: fmax Problem: Defect code : 1. Error Missing MX shading where the text refers to NaNs. Action: Add MX shading to "NaN arguments shall ... choose the numeric value" on lines 12225-12227, and to the whole of line 12231. _____________________________________________________________________________ EDITORIAL Enhancement Request Number 2 gwc@opengroup.org fmin (rdvk# 3) [gwc fmin NaN] Thu, 22 Aug 2002 16:34:28 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 380 Line: 12258-12264 Section: fmin Problem: Defect code : 1. Error Missing MX shading where the text refers to NaNs. Action: Add MX shading to "NaN arguments shall ... choose the numeric value" on lines 12258-12260, and to the whole of line 12264. _____________________________________________________________________________ EDITORIAL Enhancement Request Number 3 gwc@opengroup.org Defect in XSH pthread_attr_setstack (rdvk# 1) [gwc pthread_attr_setstack] Mon, 19 Aug 2002 17:25:57 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 1005 Line: 31731 Section: pthread_attr_setstack Problem: Defect code : 1. Error The margin code on the pthread_attr_setstack pointer page does not match the pthread_attr_getstack page (that it points to). Action: Change the margin code on page 1005 to match the codes in the SYNOPSIS on page 993. _____________________________________________________________________________ OBJECTION Enhancement Request Number 4 drepper@redhat.com Defect in XSH pthread_cond_timedwait() (rdvk# 4) {ud-cv-1} Thu, 22 Aug 2002 20:17:11 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_____OPEN Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 1033 Line: 32522 Section: pthread_cond_timedwait() Problem: Defect code : 1. Error The error section for pthread_cond_tiemdwait() and pthread_cond_wait() currently says: 32518 ERRORS 32519 The pthread_cond_timedwait( ) function shall fail if: 32520 [ETIMEDOUT] The time specified by abstime to pthread_cond_timedwait( ) has passed. 32521 The pthread_cond_timedwait( ) and pthread_cond_wait( ) functions may fail if: 32522 [EINVAL] The value specified by cond, mutex, or abstime is invalid. There are a number of things wrong: - pthread_cond_wait() has no abstime parameter; - the recognition of an invalid abstime parameter must not be optional. It isn't anywhere else. Action: Change the beginning of the ERRORS section above to: ERRORS The pthread_cond_timedwait( ) function shall fail if: [ETIMEDOUT] The time specified by abstime to pthread_cond_timedwait( ) has passed. [EINVAL] The value specified by abstime is invalid. The pthread_cond_timedwait( ) and pthread_cond_wait( ) functions may fail if: [EINVAL] The value specified by cond or mutex is invalid. I.e., create an [EINVAL] case in the "shall" section.