<html><body>
<p><font size="2" face="sans-serif">2014/01/07, 12:00 EST:</font><br>
<font size="2" face="sans-serif"> </font><font size="2" face="sans-serif"><b>Attendees</b></font><font size="2" face="sans-serif">: Jim, Rajan, Fred, David, Ian</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> New agenda items:</b></font><br>
<font size="2" face="sans-serif"> Preliminary responses to Joseph Myers emails</font><br>
<font size="2" face="sans-serif"> Previously undone action items</font><br>
<font size="2" face="sans-serif"> Discussion of email from Paul Eggert regarding names in part 4</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> Old action items:</b></font><br>
<font size="2" face="sans-serif"> Jim: Look into using the Wiki as a backup for the documents in Word format. - Most current version has been put up with PDF as well. Keep this item open. - Continuing to be done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Look for opportunities for shortening function lists by removing suffixes. - Not done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Send a note to the IEEE-754 group to get review of the draft from them. - Done</font><br>
<br>
<font size="2" face="sans-serif"> Jim: Part 3: Bring up the clause letter numbering issue at the WG14 meeting and get direction on where to put it (since the C Standard editor is normally there). - Not done</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Get a WG14 document number and post it and ask for review from the 754 group as well. - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 5: Fred's note first comment (2013/12/12 note) - Jim to fix. - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 6: Fred's note second comment (2013/12/12) - Add to the description of atan2pi that atan2pi is atan2/pi. - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 10: Leave issue 2 but add in other log*p* naming suggestions made as part of the issue. - Done as issue 1</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 11: See if the issue 3 comment can fit in the binding clause. - Done as clause 6</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 13: Add in the comment from 754 describing where this powr function comes from. - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 15: Lines 14, 20 boundaries should be -1 not 0. Also the x should be lower case (including line 26). - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 16: Make the change to the sum range to follow C indexes. Applies to later functions using similar notation (up to page 19). - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 18: Line 17: sumabs -> sumprod. - Done</font><br>
<font size="2" face="sans-serif"> Fred: Part 4: Page 18: sumprod: See if the arrays have to be non-overlapping and to see if we need to add restrict here. - Done. No restrict needed.</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 21: Line 10: Change (sum) -> (each of which is a sum) - Done</font><br>
<font size="2" face="sans-serif"> David: Part 4: Page 21: Email other suggestions to the group for action item above. - Done</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Add in the 754 operation to C function name binding table as in previous parts into this part. - Done as a separate table</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Get a WG14 document number and post it and ask for review from the 754 group as well. - Done</font><br>
<br>
<font size="2" face="sans-serif"><b> Next Meeting:</b></font><br>
<font size="2" face="sans-serif"> February 13th, 2014, 12:00 EST, 9:00 PDT</font><br>
<font size="2" face="sans-serif"> Same teleconference number.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> New action items:</b></font><br>
<font size="2" face="sans-serif"> Jim: Backup the documents in Word format. - Most current version has been put up. Keep this item open.</font><br>
<font size="2" face="sans-serif"> Current files: <a href="http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp1.docx">http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp1.docx</a></font><br>
<font size="2" face="sans-serif"> Current files: <a href="http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp2.docx">http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp2.docx</a></font><br>
<font size="2" face="sans-serif"> Current files: <a href="http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp3.docx">http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp3.docx</a></font><br>
<font size="2" face="sans-serif"> Current files: <a href="http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp4.docx">http://wiki.edg.com/twiki/pub/CFP/WebHome/cfp4.docx</a></font><br>
<font size="2" face="sans-serif"> Note: Should also keep versions that are equivalent to PDF's.</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Look for opportunities for shortening function lists by removing suffixes.</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Bring up the clause letter numbering issue at the WG14 meeting and get direction on where to put it (since the C Standard editor is normally there). Jim will email Larry about this since he will not make the meeting.</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Page viii: Reword to make the double format types clearer. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Fix the typo's listed by Joseph. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Page 3: Add in the macro as suggested. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> All: Part 3: Page 9: Look at this and decide what we should do for decimal floating types. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> All: Part 3: Page 11: Look at this and decide what we should do for the _FloatN* types and how to make it clearer what we want. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Page 32: Item 2: Mark this as an open issue. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Page 32: Item 3: Check and add if needed. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 3: Page 34-36: Check and add if needed. (Joseph's 2014/01/06 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Create a spreadsheet of log and exp functions and list the alternatives to see which conventions are being broken.</font><br>
<font size="2" face="sans-serif"> All: Part 4: Group to review the spreadsheet above and choose the best (least worse) naming scheme.</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Attempt to make the changes as described in the "General comment" part of the email. (Joseph's 2014/01/07 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Fix the typo's listed by Joseph. (Joseph's 2014/01/07 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 3: Item 2: Look into how to address this. (Joseph's 2014/01/07 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 14: Add in a footnote to the end of the description saying "cr" stands for correctly rounded. (Joseph's 2014/01/07 email)</font><br>
<font size="2" face="sans-serif"> Jim: Part 4: Page 16: Item 2: Look into rewording (ex. remove NaN specifications) to make this clearer. (Joseph's 2014/01/07 email)</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> Discussion:</b></font><br>
<font size="2" face="sans-serif"> Part 1: Out for ISO DTS ballot. Ballot ends March 5th, 2014.</font><br>
<font size="2" face="sans-serif"> No updates.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> Part 2: Out for first ISO ballot (PDTS). Ballot ends March 10th, 2014.</font><br>
<font size="2" face="sans-serif"> No updates.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> Part 3: (<a href="http://wiki.edg.com/twiki/pub/CFP/WebHome/n1784.pdf">http://wiki.edg.com/twiki/pub/CFP/WebHome/n1784.pdf</a>)</font><br>
<font size="2" face="sans-serif"> Joseph's 2014/01/06 email:</font><br>
<font size="2" face="sans-serif"> Jim: Addressing the complicated layout can be doing the C11 + all changes draft idea we have talked about before. It could be done as a project for an intern.</font><br>
<font size="2" face="sans-serif"> Fred: Larry has a very modified version of the standard source. It would be very hard for anyone else to do it.</font><br>
<font size="2" face="sans-serif"> Page viii: A rewording here should handle this.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page viii: Reword to make the double format types clearer.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Fix the typo's listed by Joseph.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page 3: Add in the macro as suggested.</font><br>
<font size="2" face="sans-serif"> Page 9: We need to make the decision on whether to include the extended decimal types as decimal floating types.</font><br>
<font size="2" face="sans-serif"> Decimal floating types is a defined term whereas binary floating types is not so no parallel there.</font><br>
<font size="2" face="sans-serif"> *All: Part 3: Page 9: Look at this and decide what we should do for decimal floating types.</font><br>
<font size="2" face="sans-serif"> Page 11: Similar to the last comment.</font><br>
<font size="2" face="sans-serif"> *All: Part 3: Page 11: Look at this and decide what we should do for the _FloatN* types and how to make it clearer what we want.</font><br>
<font size="2" face="sans-serif"> Page 32: The macros were not intended as feature test macros even though they could be used that way.</font><br>
<font size="2" face="sans-serif"> Rajan: Any other ones like this in the C standard? Complex is close but not the same (since it is a group of types).</font><br>
<font size="2" face="sans-serif"> Basically, we should follow the C standard policy/format for these.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page 32: Item 2: Mark this as an open issue.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page 32: Item 3: Check and add if needed.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page 34-36: Check and add if needed.</font><br>
<font size="2" face="sans-serif"> Page 41: By keeping the names reserved, it helps implementations that supports the types. It should only apply if the TS macro is specified of course.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 3: Page 41: Find a way to say the names should be reserved (if adhering to this TS) even if the types do not exist to enhance portability.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> Part 4:</font><br>
<font size="2" face="sans-serif"> Naming of log21p: Underscore is an option.</font><br>
<font size="2" face="sans-serif"> Jim: The reduction and scaled functions with underscores are specialized family but the general point about no underscores is still valid.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Create a spreadsheet of log and exp functions and list the alternatives to see which conventions are being broken.</font><br>
<font size="2" face="sans-serif"> *All: Part 4: Group to review the spreadsheet above and choose the best (least worse) naming scheme.</font><br>
<font size="2" face="sans-serif"> Joseph's 2014/01/07 email (first):</font><br>
<font size="2" face="sans-serif"> Jim: There has been no attempt to go through the math functions and go through the potential errors for the IEEE formats</font><br>
<font size="2" face="sans-serif"> Fred: I want the main body to also do what Joseph wants.</font><br>
<font size="2" face="sans-serif"> Jim: Unlikely to happen since the statement of the error conditions is very tricky.</font><br>
<font size="2" face="sans-serif"> Jim: If you don't conform to Annex F you have a huge latitude to what you can do and we are doing that for the new functions as well.</font><br>
<font size="2" face="sans-serif"> General comment: Agree in general.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Attempt to make the changes as described in the "General comment" part of the email.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Fix the typo's listed by Joseph.</font><br>
<font size="2" face="sans-serif"> The error cases: The C standard doesn't normally list this explicitly as suggested so it is not done here. Still need review the items though.</font><br>
<font size="2" face="sans-serif"> Page 3: Jim: The functions aren't declared unless the types are. We can make this an explicit statement.</font><br>
<font size="2" face="sans-serif"> Also the style in Part 3 and this (part 4) need to be consistent.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Page 3: Item 2: Look into how to address this.</font><br>
<font size="2" face="sans-serif"> Page 14: Jim: Ideally we would like to define them, and am surprised we have not said that already somehow.</font><br>
<font size="2" face="sans-serif"> It fits what is already there in 7.31 (like cerf in 7.31.1).</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Page 14: Add in a footnote to the end of the description saying "cr" stands for correctly rounded.</font><br>
<font size="2" face="sans-serif"> Page 15: Symmetries need to be reviewed to ensure they are in Annex F.</font><br>
<font size="2" face="sans-serif"> Page 16: Item 1.2: 754 says compoundn(x, 0) should return 1 for x >= -1, for x = inf, and x = qNaN.</font><br>
<font size="2" face="sans-serif"> Jim has sent out a note asking 754 why NaN does not give NaN.</font><br>
<font size="2" face="sans-serif"> Item 2: The NaN case is not intended to raise invalid. All numbers excludes NaN's.</font><br>
<font size="2" face="sans-serif"> *Jim: Part 4: Page 16: Item 2: Look into rewording (ex. remove NaN specifications) to make this clearer.</font><br>
<font size="2" face="sans-serif"> We can use cr_ as correctly rounded function prefix.</font><br>
<font size="2" face="sans-serif"> Joseph's 2014/01/07 email (second): Valid comment. We need to make it clearer.</font><br>
<br>
<font size="2" face="sans-serif">Regards,<br>
<br>
Rajan Bhakta<br>
z/OS XL C/C++ Compiler Technical Architect<br>
ISO C Standards Representative for Canada<br>
C Compiler Development<br>
Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</font></body></html>