<font size=2 face="sans-serif"><b>TS 18661-5 Update [N 2004] and Slide
Deck [N 2005]</b></font><br><font size=2 face="sans-serif"><b> Can go directly to DTS instead
of PDTS.</b></font><br><font size=2 face="sans-serif"><b> No objection to going to DTS
or to ballot.</b></font><br><br><br><font size=2 face="sans-serif"> Adding Fundamental Type for short
float [N 2016]</font><br><font size=2 face="sans-serif"> Use Part 3 type with the
encoding/conversion functions to get any other type.</font><br><font size=2 face="sans-serif"> Not restricting sizes
makes it useless for actual computations.</font><br><font size=2 face="sans-serif"> 5.3) Without restricting
sizes, you can't be sure.</font><br><font size=2 face="sans-serif"> 5.5) Can get different
results by conversion to float for some functions vs keeping short float.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Requiring conversion from
short float to float does not make sense since there could be some values
that aren't representable as floats (more accurate as short float).</font><br><font size=2 face="sans-serif"> Jens:</font><br><font size=2 face="sans-serif"> - Don't like the syntax
(multiple keywords for a type).</font><br><font size=2 face="sans-serif"> - Are these required by
C or optional?</font><br><font size=2 face="sans-serif"> - Implications with complex?</font><br><font size=2 face="sans-serif"> - What about tgmath?</font><br><font size=2 face="sans-serif"> Response: Easy to implement
a wrapper.</font><br><font size=2 face="sans-serif"> Derek: Adding information
in float.h for the limits would make it useful.</font><br><font size=2 face="sans-serif"> _Float16 is not defined
as per float and double. This proposal allows this.</font><br><font size=2 face="sans-serif"> Jens: Have extended floating
point types.</font><br><font size=2 face="sans-serif"> Andrew: Since everything
uses the 'half' keyword, why use 'short float'?</font><br><font size=2 face="sans-serif"> Was _Float8x considered?
Not IEEE so no.</font><br><font size=2 face="sans-serif"> float is not good enough
since 5.2.4.2.2 requires at least 6 digits.</font><br><font size=2 face="sans-serif"> Willem: How about making
it a TS?</font><br><font size=2 face="sans-serif"> Straw poll: Should WG14
continue along the lines of N2016? 18/1/5. Consensus to move forward with
this.</font><br><font size=2 face="sans-serif"> Paper solicited from the
authors.</font><br><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><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</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">04/11/2016 03:01 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Cfp-interest]
C Standard meeting 18661 DR's result</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 noshade><br><br><br><font size=2 face="sans-serif">Hi,</font><font size=3><br></font><font size=2 face="sans-serif"><br>In the C meeting, the review of the proposed defects and resolutions for
the IEEE 754 C binding Technical Specification came up with the following:</font><font size=3><br></font><font size=2 face="sans-serif"><br> TS 18661 DR's: [N 2029]<br> TS18661-1:<br> 1) Marked as DR1-1<br> 2) Marked as DR2-1<br> 3) Editorial. Can be published with a TC.<br> 4) Marked as DR3-1<br> <br> TS18661-2:<br> 1) Editorial.</font><font size=3><br></font><font size=2 face="sans-serif"><br> TS18661-3:<br> 1) Editorial<br> 2) Editorial<br> 3) Marked as DR1-3<br> <br>Result: Accepting all Suggested Technical Corrigendum's as Proposed Technical
Corrigendum's.</font><font size=3><br></font><font size=2 face="sans-serif"><br>I will be presenting Part 5 right after this current discussion of N2016
(the half float type proposal) and will let you know how it goes.</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<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><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest"><tt><font size=2>http://mailman.oakapple.net/mailman/listinfo/cfp-interest</font></tt></a><tt><font size=2><br></font></tt><br><BR>