<font size=2 face="sans-serif">N1591 (updated) - IEEE 754-2008 C binding,
Monday, 2012/02/13, 11:05 am, Jim Thomas presenting in the Spring 2012
ISO JTC1/SC22/WG14 meeting.</font>
<br>
<br><font size=2 face="sans-serif"><b>Preamble:</b></font>
<br>
<br><font size=2 face="sans-serif">IEEE 754-2008 It is an ISO/IEEE/IEC
standard. IEC 60559:2011.</font>
<br><font size=2 face="sans-serif">It will be a single document with 5
separate parts.</font>
<br>
<br><font size=2 face="sans-serif"><b>Issue discussions:</b></font>
<br>
<br><font size=2 face="sans-serif">Issue 1: Free standing vs hosted (Clause
2, p7)</font>
<br><font size=2 face="sans-serif"> - Can do something like stdint
and inttypes, one being a subset of another.</font>
<br><font size=2 face="sans-serif"> Ex. We can make the Floating
Point aspects into a special subset that could be used to make it easy
for freestanding implementations.</font>
<br><font size=2 face="sans-serif"> Consensus to move forward to
allow freestanding implementations</font>
<br><font size=2 face="sans-serif">Note: Most people in MISRA would support
this</font>
<br>
<br>
<br><font size=2 face="sans-serif">Issue 2: Should we add a WANT macro?</font>
<br><font size=2 face="sans-serif"> - Should do this to avoid namespace
pollution.</font>
<br><font size=2 face="sans-serif">Consensus was to add this and to use
a number of separate macros.</font>
<br>
<br><font size=2 face="sans-serif">Issue 3: Table 1: How can it be improved?</font>
<br><font size=2 face="sans-serif"> - Put forward references to the
section in the C Standard where the details are into a third column. Note:
A particular function may not be completely referenceable but that is also
interesting.</font>
<br><font size=2 face="sans-serif">Consensus was to replace F.3 with the
table with the extra column(s) with the forward reference(s).</font>
<br>
<br><font size=2 face="sans-serif">Issue 4: Withdrawn to bring up later
in a different part (alternate exception handling).</font>
<br>
<br><font size=2 face="sans-serif">Issue 5: Call made through function
pointers - All function calls are function pointer calls</font>
<br><font size=2 face="sans-serif"> - It could be a function that
returns a function pointer.</font>
<br><font size=2 face="sans-serif"> - Do something like tgmath where
you just specify the function and the correct rounded type of function
is chosen.</font>
<br><font size=2 face="sans-serif"> - Whatever solution has to consider
inlining.</font>
<br><font size=2 face="sans-serif">Still open.</font>
<br>
<br><font size=2 face="sans-serif">Issue 6: Integer width macros - Is this
where this belongs? Could be outside the Floating Point TS.</font>
<br><font size=2 face="sans-serif">Consensus was to keep it here as part
of the floating point TS.</font>
<br>
<br><font size=2 face="sans-serif">Issue 7: Withdrawn - We will work on
this: Names are not quite perfect.</font>
<br>
<br><font size=2 face="sans-serif">Issue 8: pg. 29: Should the 7.12 spec
of llogb require a domain error for finite out of range cases?</font>
<br><font size=2 face="sans-serif">Keep it the same as ilogb unless it
changes based on Fred's papers. (Note: Fred's papers resulted in no change
at this time.)</font>
<br>
<br><font size=2 face="sans-serif"><b>Other comments:</b></font>
<br><font size=2 face="sans-serif"> It
is hard to tell where the text replacement starts and ends. Can it be clarified?</font>
<br><font size=2 face="sans-serif">
Ex. Page 10</font>
<br><font size=2 face="sans-serif"> Suggestion: Put the old text
in a box with the replacement text in another box.</font>
<br><font size=2 face="sans-serif"> Note:
Cannot be published with strikethroughs, bold for inserts, etc. but can
be seen as that way for presentation. A good example of how to do it is
the embedded TR and the DFP TR.</font>
<br>
<br><font size=2 face="sans-serif"><b>Next steps:</b></font>
<br><font size=2 face="sans-serif">1) Continue as we're working</font>
<br><font size=2 face="sans-serif">2) Create a new work item for WG14 -
Jim and John Benito to work on this.</font>
<br><font size=2 face="sans-serif">WG14 can issue the document as each
national body says they don't have a document.</font>
<br><font size=2 face="sans-serif">Consensus was that this is ready to
be a work item for WG14.</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@ca.ibm.com, Rajan Bhakta/Toronto/IBM<br>
Telephone: (905) 413-3995</font>