<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.9600.19431"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial>As always, thanks for the excellent
notes!!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial>One update: <FONT color=#000000 face="">*AI*: Jim:
Ensure thin spaces are put where needed in
C2x_proposal_-_powr_justification_wording-20200104.pdf. Ex. Between the e and y
in the "e^y log x" in three places. </FONT></FONT></SPAN></DIV><SPAN
class=605213719-09012020><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000></FONT>
<DIV dir=ltr align=left><BR> should read. <FONT color=#000000 face="">*AI*:
Jim: Ensure thin spaces are put where needed in
C2x_proposal_-_powr_justification_wording-20200104.pdf. Ex. Between the e and y
in the "e^y log x" in<FONT color=#ff0000> four</FONT> places.
</FONT><BR></FONT></SPAN><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial>Mike</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=605213719-09012020><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=605213719-09012020></SPAN><SPAN
class=605213719-09012020><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> cfp-interest-bounces@oakapple.net
[mailto:cfp-interest-bounces@oakapple.net] <B>On Behalf Of </B>Rajan
Bhakta<BR><B>Sent:</B> 09 January 2020 17:39<BR><B>To:</B>
cfp-interest@oakapple.net<BR><B>Subject:</B> [Cfp-interest 1454] WG14 IEEE
754-C binding meeting minutes2020/01/09<BR></FONT><BR></DIV>
<DIV></DIV><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
<B>Attendees</B>: Rajan, Jim, Mike, Ian, David H.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> New agenda
items:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
None.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> Carry over action
items:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> CFP: Put the
tgmath redefinition as a proposal to the standard once we have a base document
with TS Part 3 in it.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B>
Last meeting action items:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Fred: Update
erange proposal based on CFP 1437 and CFP teleconference discussion. -
Unknown.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Submit
</SPAN><A href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_NaN_and_infinity_macros_-_20191108.pdf
to WG14. - Done.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Rajan: Compile
example code in </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf.
- Done.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Choose how
to attach footnote in </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf;
mention the other approach in the problem description. - Done.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Draft a
paper proposing changing the “cr” prefix for correctly rounded functions to
“cr_”. Include with other suggested changes in response to Jens’s naming
paper. - Done.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> David H: Draft
words to recommend honoring properties (Ex. even/odd, periodicity) of math
functions that would follow automatically from correct rounding. - Not
done.</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Find a place for words about math function properties.
Coordinate with David H (previous AI). - Not done.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Comments:</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Ian: Monoticity as well and making correctly rounded be recommended
practice.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
David: We can say if it is correctly rounded, they get the properties
anyways.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Draft a
proposal to change the return words for powr and add the footnote (presented
in the meeting) to justify powr. - Done.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> New action
items:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Look at
seeing what would be involved in removing Annex J types that already have the
same basic types.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Get a WG14
document number and submit
C2x_proposal_-_why_no_wide_string_strfrom_functions-
20191230.pdf.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Get a WG14
document number and submit
C2x_proposal_-_names_and_locations-20200105.pdf.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Ensure
natural log is written as log in the standard (regarding
C2x_proposal_-_powr_justification_wording-20200104.pdf). </SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Ensure
thin spaces are put where needed in
C2x_proposal_-_powr_justification_wording-20200104.pdf. Ex. Between the e and
y in the "e^y log x" in three places. </SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Update
links on the C FP wiki to point to the latest drafts of the TS parts and look
into having a section for working drafts.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Rajan: Ensure
casting to _Float16 won't cause a problem with the using INFINITY wherever a
constant expression can be used change we proposed.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> Next
Meeting(s):</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Wednesday,
February 19th, 2020, 11:00 EST, 8:00 PST, 4PM UTC</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Same
teleconference number.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Please notify
the group if this time slot does not work.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim away
Jan. 14-28th.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B>
Discussion:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> 754
revision:</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Done!</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
CFP 1443 has the paper/article David wrote.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Drop
this agenda item.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> C++
Liaison:</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Nothing.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> C2X integration
(</SPAN><A
href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">):</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Draft
with TS 1, 2, and 4a (Latest C2X draft: </SPAN><A
href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2454.pdf"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2454.pdf</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">, also as link on CFP
wiki)</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Part 3 - Was in a branch as work in progress prior to Jens
stepping down as editor. As Annex J.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Part 4b
- Looking as an updated TS.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Part
5a,b,c,d</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
C2X target: 2023</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim:
Idea is to propose IEEE 2019 binding in the next C meeting. We can discuss
next CFP meeting.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim:
Question: Should we remove value redundant types from Annex J? Ex. _Float32
being the same as float, _Float64 being the same as double, _Float32x being
the same as double or long double. We added this as consistency, but the
initial goal was just to provide nomenclature for the types.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
*AI*: Jim: Look at seeing what would be involved in removing Annex J types
that already have the same basic types.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> Action item
details:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Fred: Update
erange proposal based on CFP 1437 and CFP teleconference
discussion.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Submit </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_NaN_and_infinity_macros_-_20191108.pdf
to WG14. (</SPAN><A href="http://wiki.edg.com/pub/CFP/WebHome/n2469.pdf"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/n2469.pdf</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">)</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Looks
good.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Rajan: Compile
example code in </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf.
(See Rajan’s CFP 1441)</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Looks
good.</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Choose how
to attach footnote in </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf;
mention the other approach in the problem description. </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions-"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions-</SPAN></A><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">20191230.pdf</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Looks
good.</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
*AI*: Jim: Get a WG14 document number and submit
C2x_proposal_-_why_no_wide_string_strfrom_functions-
20191230.pdf.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Draft a paper proposing changing the “cr” prefix for correctly
rounded functions to “cr_”. Include with other suggested changes in response
to Jens’s naming paper. </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_names_and_locations-20200105.pdf"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_names_and_locations-20200105.pdf</SPAN></A><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> cr_ was
never proposed by any paper.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Moving
the SNAN macros does follow the suggestion of renaming, but also moves it
which was not previously proposed.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> *AI*:
Jim: Get a WG14 document number and submit
C2x_proposal_-_names_and_locations-20200105.pdf.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
David H: Draft words to recommend honoring properties of math functions
that would follow automatically from correct rounding.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Still to
do.</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim: Find a
place for words about math function properties. Coordinate with David H
(previous AI).</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Suggest
adding a title to the table in F.3#23.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
David: Functions that IEC 60559 recommends be correctly
rounded</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
David: The first table title should also be changed to distinguish this table.
Ex. Binding of operations required by IEC 60559; Binding of functions or
operations recommended by IEC 60559.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Or "Bindings of operations required by IEC 60559"; "Bindings of
operations recommended by IEC 60559" See C FP 1453</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Suggest
adding a second recommended practice to F.10.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Draft a proposal to change the return words for powr and add the
footnote (presented in the meeting) to justify powr. </SPAN><A
href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_powr_justification_wording-20200104.pdf"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif; COLOR: blue">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_powr_justification_wording-20200104.pdf</SPAN></A><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> *AI*:
Jim: Ensure natural log is written as log in the standard (regarding
C2x_proposal_-_powr_justification_wording-20200104.pdf). </SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> *AI*:
Jim: Ensure thin spaces are put where needed in
C2x_proposal_-_powr_justification_wording-20200104.pdf. Ex. Between the e and
y in the "e^y log x" in three places. </SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"><B> Other
issues:</B></SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> WG14 editor
change</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim and Rajan meeting with David Keaton regarding finishing off
the work.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Is
“Floating-point extensions for C” still an appropriate description of CFP
work? See Mike’s email CFP 1445.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim:
"IEC 60559 Floating point support in C"?</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Sounds
good.</SPAN><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Also remove reference to 2008 on the
website.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim:
Update links to the published TS's on the website.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Rajan: Link published for all, and have working drafts for any ones with
changes or that are not in C2X.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> *AI*:
Jim: Update links on the C FP wiki to point to the latest drafts of the TS
parts and look into having a section for working drafts.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Issue for
_Float16: INFINITY has type float so widens operations with _Float16
operands.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif"> Jim:
Ideally NAN and INFINITY macros would be _Float16 if it was supported. We
could add a comment suggesting putting a cast to _Float16 in front of INFINITY
if you really wanted operations to stay in _Float16 type.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Ian: Doesn't work for SNAN's.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
Jim: Not an issue since we have type'd versions of those.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
May be an issue for constant expressions.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">
*AI*: Rajan: Ensure casting to _Float16 won't cause a problem with the using
INFINITY wherever a constant expression can be used change we
proposed.</SPAN><BR><BR></BLOCKQUOTE></BODY></HTML>