<html><body>
<p><font size="2" face="sans-serif">One addendum (sorry about missing it):</font><br>
<br>
<font size="2" face="sans-serif">Constant rounding modes: Decided to keep two separate #pragma's (one for standard floating rounding mode and one for decimal floating rounding mode)</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><br>
<br>
<img width="16" height="16" src="cid:1__=09BBF156DFF1A8288f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Rajan Bhakta---08/08/2013 01:01:47 PM---2013/08/08: Attendees: Jim, Mike, David, Ian, Rajan, Marius"><font size="2" color="#424282" face="sans-serif">Rajan Bhakta---08/08/2013 01:01:47 PM---2013/08/08: Attendees: Jim, Mike, David, Ian, Rajan, Marius (10:00 PDT)</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Rajan Bhakta/Houston/IBM@IBMUS</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"cfp-interest@oakapple.net" <cfp-interest@oakapple.net>, </font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">08/08/2013 01:01 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[Cfp-interest] WG14 IEEE 754-C binding meeting minutes 2013/08/08</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Sent by: </font><font size="1" face="sans-serif">cfp-interest-bounces@oakapple.net</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="2" face="sans-serif">2013/08/08:<br>
</font><font size="2" face="sans-serif"><b>Attendees:</b></font><font size="2" face="sans-serif"> Jim, Mike, David, Ian, Rajan, Marius (10:00 PDT)<br>
<br>
</font><font size="2" face="sans-serif"><b>Old action items:</b></font><font size="2" face="sans-serif"><br>
Jim to send email about WANT macros - Done<br>
All to review July 10th email (5.2.4.2.2 reorg) - Done<br>
<br>
</font><font size="2" face="sans-serif"><b>Next meeting:</b></font><font size="2" face="sans-serif"><br>
September 10th, 2013, 12:00 EST, 9:00 PDT<br>
Same teleconference number<br>
<br>
</font><font size="2" face="sans-serif"><b>New action items:</b></font><font size="2" face="sans-serif"><br>
Jim: Changes to make to part 2:<br>
Page 1: does not cover -> neither<br>
Page 3: Remove lists unless there is an actual change in the identifiers<br>
Page 8: Look at the phrase "they have the" to see if other places may have the existing wording<br>
Page 19: Line 4: Font on stdio.h is wrong<br>
Jim: Changes to make to all parts: Want macro name: __STDC_WANT_IEC_60559_{BFP, DFP, TYPES, FUNCS, ...}__<br>
<br>
</font><font size="2" face="sans-serif"><b>Current status:</b></font><font size="2" face="sans-serif"><br>
Ballot on part one ends on August 16th and this is the first time we get to look at comments<br>
Jim will be on vacation from the 16th to the 29th<br>
WG14 mailing deadline is September 2nd, but John will allow posting docs until September 16th to still discuss it in the meeting<br>
WG14 meeting: September 30th to October 3rd<br>
Jim can work on speculative draft based on comments discussing over email before the September meeting<br>
Jim will get the part 2 draft ready for the WG14 posting<br>
<br>
</font><font size="2" face="sans-serif"><b>Part 2 discussion:</b></font><font size="2" face="sans-serif"><br>
*Page 1: does not cover -> neither<br>
Page 3: Grouping the changes here is a lot of information at the start, but it seems to be easier for implementers and for maintenance.<br>
*The lists are only present for review purposes, but will be removed for the actual change<br>
We can have a list of identifiers introduced per want macro.<br>
Page 8:<br>
Mike: Rather than "they have the" -> "they correspond to the"<br>
*Jim: Other places may have the existing wording. I will check.<br>
Correspond seems too weak.<br>
Page 11:<br>
Should we make a corresponding change to the standard floating types even though the clarification has nothing to do with the new floating point standard update.<br>
Rajan: Better to try and pass part 1 and part 2 and handle it as a DR<br>
Mike: We could also handle this as part of the comments for part 1<br>
Jim: We can provide editorial suggestions based on the ballot even if there were no comments on this part<br>
<br>
Do we want to add in the other -ve value text to allow implementation defined behavior?<br>
We can come back to this in Part 3 if needed.<br>
<br>
*Page 19: Line 4: Font on stdio.h is wrong<br>
<br>
Page 21:<br>
This is different from other standard pragmas in that some implementations do macro expansion in pragmas and others don't. Since the values are std defined pragmas this may have implications we have not considered.<br>
<br>
</font><font size="2" face="sans-serif"><b>Want macro name:</b></font><font size="2" face="sans-serif"><br>
Keep functional part for code readability<br>
Drop EXT#, LIB since they add no value<br>
Keep IEC, 60559 to identify it<br>
*Name: __STDC_WANT_IEC_60559_{BFP, DFP, TYPES, FUNCS, ...}__<br>
<br>
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><tt><font size="2">_______________________________________________<br>
Cfp-interest mailing list<br>
Cfp-interest@oakapple.net<br>
</font></tt><tt><font size="2"><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest">http://mailman.oakapple.net/mailman/listinfo/cfp-interest</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</body></html>