<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Rajan,<div class=""><br class=""></div><div class="">Thanks for the summary. I have a few questions below.</div><div class=""><br class=""></div><div class="">Safe travel,</div><div class=""><br class=""></div><div class="">Jim<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 16, 2018, at 5:27 PM, Rajan Bhakta <<a href="mailto:rbhakta@us.ibm.com" class="">rbhakta@us.ibm.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><font size="2" face="sans-serif" class="">Hello,</font><br class=""><br class=""><font size="2" face="sans-serif" class="">Here is a summary of all the decisions
reached in WG14 regarding the floating point study group topics of interest
to date. The major items are that we need to provide updated Parts 1 and
2 containing all closed defects (as of this WG14 meeting, all changed status
given below) to the WG14 editors, and to create a new version of Part 3
that is a conditionally normative annex (if we want Part 3 to be a part
of C2X) as a separate proposal.</font><br class=""><br class=""><font size="3" face="Times-Roman" class=""><b class="">Action items:</b></font><br class=""><font size="3" face="Times-Roman" class=""> - Give all (CR/DR) changes integrated
into the Floating Point TS’s by the end of this meeting to the WG14 editors
for Parts 1 and 2. Subsequent changes will be based on the C2X working
draft.</font></div></blockquote><br class=""></div><div>As elaborated below (For the C2X Proposals, Parts 1 and 2 …), right?</div><div><blockquote type="cite" class=""><div class=""><br class=""><font size="2" face="sans-serif" class=""><b class="">TS CR's:</b></font><br class=""><font size="3" face="Times-Roman" class=""> DR17: Move to closed.</font><br class=""><font size="3" face="Times-Roman" class=""> DR18: Move to closed.</font><br class=""><font size="3" face="Times-Roman" class=""> DR19: Move to closed.</font><br class=""><font size="3" face="Times-Roman" class=""> DR13: See N2252. Move
to review.</font><br class=""><font size="3" face="Times-Roman" class=""> DR16: Move to review.</font><br class=""><font size="3" face="Times-Roman" class=""> DR20: See N2254. Move
to review.</font><br class=""><font size="3" face="Times-Roman" class=""> DR21: See N2283. Move
to review.</font><br class=""><font size="3" face="Times-Roman" class=""> DR22: See N2255. Move
to review.</font><br class=""><br class=""><font size="2" face="sans-serif" class=""><b class="">For proposed CR/DR's:</b></font><br class=""><font size="3" face="Times-Roman" class="">P2 CR for llquantep invalid case [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2262.pdf" class=""><font size="3" color="#0000e0" face="Times-Roman" class=""><u class="">N
2262</u></font></a><font size="3" face="Times-Roman" class="">]</font><br class=""><font size="3" face="Times-Roman" class=""> CR23. Move to review.</font><br class=""><font size="3" face="Times-Roman" class="">P1 CR for remainder NaN case [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2272.pdf" class=""><font size="3" color="#0000e0" face="Times-Roman" class=""><u class="">N
2272</u></font></a><font size="3" face="Times-Roman" class="">]</font><br class=""><font size="3" face="Times-Roman" class=""> CR24. Move to review.</font><br class=""><font size="3" face="Times-Roman" class="">P1 CR for totalorder parameters [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2292.pdf" class=""><font size="3" color="#0000e0" face="Times-Roman" class=""><u class="">N
2292</u></font></a><font size="3" face="Times-Roman" class="">]</font><br class=""><font size="3" face="Times-Roman" class=""> CR25. Move to review. The change
will be reflected in C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Note: Jens, Blaine, Aaron, Martin:
Prefer Built In Functions. The issue is taking the address of the function.</font><br class=""><br class=""><font size="2" face="sans-serif" class=""><b class="">For the C defects:</b></font><br class=""><font size="3" face="Times-Roman" class="">Move to DR501 into review after incorporating
N2253.</font><br class=""><br class=""><font size="3" face="Times-Roman" class=""><b class="">For the C2X Proposals:</b></font><br class=""><font size="3" face="Times-Roman" class=""> Parts 1 and 2 will go in. Note
that as per above, the plan is for our group to incorporate all changes
from closed DR/CR's to the point of the end of this WG14 meeting into working
drafts of the TS parts 1 and 2 and give that to Jens and Larry for incorporation
into a working draft of C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Part 3: New types</font><br class=""><font size="3" face="Times-Roman" class=""> Looking for the
floating point study group to turn this into a conditionally normative
annex (new proposal).</font><br class=""></div></blockquote><div><br class=""></div>Hmm. The P3 specification includes changes all the way through the standard. Did WG14 give any indication of what form an acceptable annex might take?</div><div><br class=""><blockquote type="cite" class=""><div class=""><font size="3" face="Times-Roman" class=""> Part 4: Mathematical
functions:</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
add this to the working draft of C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Part 4: Reduction functions:</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
add this to the working draft of C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Part 5: Evaluation format
pragmas:</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
add this to the working draft of C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Part 5: Optimization
control pragmas</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
add this to the working draft of C2X.</font><br class=""><font size="3" face="Times-Roman" class=""> Part 5: Reproducible
results</font><br class=""><font size="3" face="Times-Roman" class=""> Not looking for
the FP study group to rework this without optimization pragma.</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
add this to the working draft of C2X.</font><br class=""></div></blockquote><div><br class=""></div>Could you say more about what “no consensus” means?</div><div><br class=""><blockquote type="cite" class=""><div class=""><font size="3" face="Times-Roman" class=""> Rounding direction macro:
Passed (Will be in C2X)</font><br class=""><font size="3" face="Times-Roman" class=""> N2123: Alternate exception
handling.</font><br class=""><font size="3" face="Times-Roman" class=""> No consensus to
do anything.</font><br class=""><br class=""><font size="2" face="sans-serif" class="">Regards,<br class=""><br class="">Rajan Bhakta<br class="">z/OS XL C/C++ Compiler Technical Architect<br class="">ISO C Standards Representative for Canada, PL22.11 Chair (USA)<br class="">C Compiler Development<br class="">Contact: <a href="mailto:rbhakta@us.ibm.com" class="">rbhakta@us.ibm.com</a>, Rajan Bhakta/Houston/IBM</font><br class="">
_______________________________________________<br class="">Cfp-interest mailing list<br class=""><a href="mailto:Cfp-interest@oakapple.net" class="">Cfp-interest@oakapple.net</a><br class="">http://mailman.oakapple.net/mailman/listinfo/cfp-interest<br class=""></div></blockquote></div><br class=""></div></body></html>