<font size=2 face="sans-serif">Looks good to me.</font>
<br>
<br><font size=2 face="sans-serif">Regards,<br>
<br>
Rajan Bhakta<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Jim Thomas <jaswthomas@sbcglobal.net></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">CFP <cfp-interest@ucbtest.org>,
</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">02/19/2013 04:50 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">[Cfp-interest] Part 3 suggested 6.2.5
[10a]</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">cfp-interest-bounces@oakapple.net</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>At the Feb CFP meeting, Rajan noted that the proposed
6.2.5 [10a] in Part 3 needs work to clarify what is required and what is
optional. The following rewrite is intended to do that. Please review.</font>
<br>
<br><font size=3>-Jim</font>
<br>
<p><font size=3>[10a] IEC 60559 specifies interchange formats, identified
by their width, which can be used for the exchange of floating-point data
between implementations. Tables 1 and 2 give parameters for the IEC 60559
interchange formats.</font>
<p><font size=3><i>Table 1 goes here</i></font>
<p><font size=3><i>Table 2 goes here</i></font>
<p><font size=3>Types designated</font>
<p><font size=3>
</font><font size=3 face="Courier New"><b>_Float</b></font><font size=3><i>N</i>,
where <i>N</i> is 16, 32, 64, or ≥ 128 and a multiple of 32</font>
<p><font size=3 face="Courier New"><b>_Decimal</b></font><font size=3><i>N</i>,
where <i>N</i> ≥ 32 and a multiple of 32</font>
<p><font size=3>support the corresponding IEC 60559 interchange formats
and are collectively called the <i>data-interchange types</i>. Each data-interchange
type has the IEC 60559 interchange format corresponding to its width and
radix. Data-interchange types that are supported by all applicable floating-point
operations are collectively called the <i>interchange floating types</i>.
An implementation that defines </font><font size=3 face="Courier New"><b>__STDC_IEC_60559_BFP__</b></font><font size=3>
shall provide </font><font size=3 face="Courier New"><b>_Float32</b></font><font size=3>
and </font><font size=3 face="Courier New"><b>_Float64</b></font><font size=3>
as interchange floating types equivalent to </font><font size=3 face="Courier New"><b>float</b></font><font size=3>
and </font><font size=3 face="Courier New"><b>double</b></font><font size=3>,
shall provide </font><font size=3 face="Courier New"><b>_Float16</b></font><font size=3>
as a data-interchange type, and may provide </font><font size=3 face="Courier New"><b>_Float16</b></font><font size=3>
as an interchange floating type. If the implementation’s </font><font size=3 face="Courier New"><b>long
double</b></font><font size=3> type has an IEC 60559 interchange format
of width <i>N</i>, then the implementation shall provide the type </font><font size=3 face="Courier New"><b>_Float</b></font><font size=3><i>N</i>
as an interchange floating type. An implementation may provide any of the
other data-interchange types and may provide any of them as interchange
floating types. </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>
<p>
<p>