<font size=2 face="sans-serif">Hi Jim, others,</font><br><br><font size=2 face="sans-serif">Answers below tagged with </font><font size=3><Rajan/></font><font size=2 face="sans-serif">.</font><br><br><font size=2 face="sans-serif">Also new updates from today:</font><br><font size=3 face="Times-Roman">6.16 pow divide-by-zero case [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2271.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2271</u></font></a><font size=3 face="Times-Roman">]</font><br><font size=3 face="Times-Roman"> Looks good to put in. It will
be added to the minutes as an item that will go into C2X.</font><br><font size=3 face="Times-Roman">6.17 Min-max functions [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2273.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2273</u></font></a><font size=3 face="Times-Roman">]</font><br><font size=3 face="Times-Roman"> FP study group to split this
into two separate proposals. One for parts 1 and 2 changes based on the
TS’s, and the other for part 3 that fits the conditionally normative part
3 annex.</font><br><font size=3 face="Times-Roman">6.18 Augmented arithmetic functions
[</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2274.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2274</u></font></a><font size=3 face="Times-Roman">]</font><br><font size=3 face="Times-Roman"> Not accepted. They said we could
bring this forward again as part of a future revision of the TS at a later
date (i.e. After the IEEE spec is published and the C2X integration of
parts 1 and 2 are in).</font><br><font size=3 face="Times-Roman"> Nothing to do at this time in
WG14, but the floating point group may want to bring this forward again
for a future revision of the TS.</font><br><font size=3 face="Times-Roman">6.19 C support for IEEE 754-201x [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2275.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2275</u></font></a><font size=3 face="Times-Roman">]</font><br><font size=3 face="Times-Roman"> David: Good job on getting ahead
of the IEEE spec and minimizing the changes needed.</font><br><font size=3 face="Times-Roman"> Priorities should be do parts
4 and 5 updates to IEEE and then rebase on C2X and then bring it forward
for a new published revision. </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, PL22.11 Chair (USA)<br>C Compiler Development<br>Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Jim Thomas <jaswthomas@sbcglobal.net></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Rajan Bhakta <rbhakta@us.ibm.com></font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">cfp-interest@oakapple.net</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/17/2018 08:17 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Cfp-interest]
Summary of C FP issues so far</font><br><hr noshade><br><br><br><font size=3>Rajan,</font><br><br><font size=3>Thanks for the summary. I have a few questions below.</font><br><br><font size=3>Safe travel,</font><br><br><font size=3>Jim</font><br><br><font size=3>On Oct 16, 2018, at 5:27 PM, Rajan Bhakta <</font><a href="mailto:rbhakta@us.ibm.com"><font size=3 color=blue><u>rbhakta@us.ibm.com</u></font></a><font size=3>>
wrote:</font><br><br><font size=2 face="sans-serif">Hello,</font><font size=3><br></font><font size=2 face="sans-serif"><br>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><font size=3><br></font><font size=3 face="Times-Roman"><b><br>Action items:</b><br> - 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><br><br><font size=3>As elaborated below (For the C2X Proposals, Parts 1 and
2 …), right?</font><br><font size=3><Rajan/>Correct</font><br><font size=2 face="sans-serif"><b><br>TS CR's:</b></font><font size=3 face="Times-Roman"><br> DR17: Move to closed.<br> DR18: Move to closed.<br> DR19: Move to closed.<br> DR13: See N2252. Move to review.<br> DR16: Move to review.<br> DR20: See N2254. Move to review.<br> DR21: See N2283. Move to review.<br> DR22: See N2255. Move to review.</font><font size=3><br></font><font size=2 face="sans-serif"><b><br>For proposed CR/DR's:</b></font><font size=3 face="Times-Roman"><br>P2 CR for llquantep invalid case [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2262.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2262</u></font></a><font size=3 face="Times-Roman">]<br> CR23. Move to review.<br>P1 CR for remainder NaN case [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2272.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2272</u></font></a><font size=3 face="Times-Roman">]<br> CR24. Move to review.<br>P1 CR for totalorder parameters [</font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2292.pdf"><font size=3 color=#0000e0 face="Times-Roman"><u>N
2292</u></font></a><font size=3 face="Times-Roman">]<br> CR25. Move to review. The change will be reflected in C2X.<br> Note: Jens, Blaine, Aaron, Martin: Prefer Built In Functions. The
issue is taking the address of the function.</font><font size=3><br></font><font size=2 face="sans-serif"><b><br>For the C defects:</b></font><font size=3 face="Times-Roman"><br>Move to DR501 into review after incorporating N2253.</font><font size=3><br></font><font size=3 face="Times-Roman"><b><br>For the C2X Proposals:</b><br> 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.<br> Part 3: New types<br> Looking for the floating point study group to turn
this into a conditionally normative annex (new proposal).</font><br><br><font size=3>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?</font><br><font size=3><Rajan/>They indicated it would be a hard problem
but they hoped we could work through it and leave it as a self contained
annex. In a hallway conversation with Jens, he seemed ambivalent whether
or not we make that self contained annex the same as other Annexes or if
we basically wrote is as changes to C2X like we have now as changes to
C11 (but not the changes to C11 + part 1 + part 2 obviously).</font><br><br><font size=3 face="Times-Roman"> Part 4: Mathematical
functions:<br> No consensus to add this to the working draft of C2X.<br> Part 4: Reduction functions:<br> No consensus to add this to the working draft of C2X.<br> Part 5: Evaluation format pragmas:<br> No consensus to add this to the working draft of C2X.<br> Part 5: Optimization control pragmas<br> No consensus to add this to the working draft of C2X.<br> Part 5: Reproducible results<br> Not looking for the FP study group to rework this
without optimization pragma.<br> No consensus to add this to the working draft of C2X.</font><br><br><font size=3>Could you say more about what “no consensus” means?</font><br><font size=3><Rajan/>Generally it is a nice way of saying "We
don't want this"</font><br><br><font size=3 face="Times-Roman"> Rounding direction macro:
Passed (Will be in C2X)<br> N2123: Alternate exception handling.<br> No consensus to do anything.</font><font size=3><br></font><font size=2 face="sans-serif"><br>Regards,<br><br>Rajan Bhakta<br>z/OS XL C/C++ Compiler Technical Architect<br>ISO C Standards Representative for Canada, PL22.11 Chair (USA)<br>C Compiler Development<br>Contact: </font><a href="mailto:rbhakta@us.ibm.com"><font size=2 color=blue face="sans-serif"><u>rbhakta@us.ibm.com</u></font></a><font size=2 face="sans-serif">,
Rajan Bhakta/Houston/IBM</font><font size=3><br>_______________________________________________<br>Cfp-interest mailing list</font><font size=3 color=blue><u><br></u></font><a href="mailto:Cfp-interest@oakapple.net"><font size=3 color=blue><u>Cfp-interest@oakapple.net</u></font></a><font size=3><br></font><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest"><font size=3>http://mailman.oakapple.net/mailman/listinfo/cfp-interest</font></a><br><br><br><BR>