<span style=" font-size:10pt;font-family:sans-serif"> <b>Attendees</b>:
Rajan, Jim, Mike, Fred, David C., David H., David Olsen (C++ Standards
committee), Ian</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">
TS 3 as an annex</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. See CFP 1386. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Added into the draft Jim sent CFP 1554.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David: Look into Jim's duplicated CFP messages. Also some missing messages
if the person was in the To list (while CFP was cc'd). David to upgrade
mailman. - Not done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Still an issue.</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">
Jim: See if N2478 changes anything for our proposals (which reference n2454).
- Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Get a paper number for CFP 1538 and submit it. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get a paper number for the paper referenced in CFP 1516 and submit
it. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Add in a note to CFP 1526 to say the cast raises no floating point
exceptions. - 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: Add a note to Part 3 as an Annex to mention the redundant decimal
suffixes (df, dd, dl vs d32, d64, d128).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Add a forward reference in X.3 to a new example for the use of encoding
conversion in the encoding functions section.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Need to look into seeing if _Imaginary types should be added to the
list of types for carg, cimag, conj, cproj, creal (p32, line 5 of </span><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20200414.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20200414.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">)
</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, May 20th, 2020, 11:00 EST, 8:00 PST, 4PM UTC</span><br><span style=" font-size:10pt;font-family:sans-serif">
ISO Zoom teleconference</span><br><span style=" font-size:10pt;font-family:sans-serif">
Please notify the group if this time slot does not work.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Zoom - Working well with the new meeting information in the email (CFP
1562).</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">
C++ Liaison:</span><br><span style=" font-size:10pt;font-family:sans-serif">
David O. joining. Interested in part 3 and Float16.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
WG14 meeting:</span><br><span style=" font-size:10pt;font-family:sans-serif">
See [Cfp-interest 1552] Fw: WG14 meeting summary of items of interest
to CFP - Filled in missing votes in 8.1</span><br><span style=" font-size:10pt;font-family:sans-serif">
Other CFP papers were not discussed. Should be on the main agenda
in the August 3-7th WG14 Freiburg meeting.</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/n2478.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2478.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">):</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 3 - Investigating updates</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 4b</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">
Proposals for IEEE-2019 support have been submitted.</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">
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">
*AI*: Jim: Add a note to Part 3 as an Annex to mention the redundant
decimal suffixes (df, dd, dl vs d32, d64, d128).</span><br><span style=" font-size:10pt;font-family:sans-serif">
We can ask WG14 to see what they want.</span><br><span style=" font-size:10pt;font-family:sans-serif">
X.8 change to refer to Annex B is good with the current WG14 direction
of having part 3 as an annex.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: For the encode functions, add an example showing the usage
for _Float16 to something like _Float32.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Should be there in p9 (X.3). We can add a forward reference
in X.3 to an example for that in the encoding functions section.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Add a forward reference in X.3 to a new example
for the use of encoding conversion in the encoding functions section.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: p32 line 5: Should imaginary be mentioned?</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Need to look into seeing if _Imaginary types should
be added to the list of types for carg, cimag, conj, cproj, creal (p32,
line 5 of </span><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20200414.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20200414.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">)</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
David: Look into Jim's duplicated CFP messages. Also some missing messages
if the person was in the To list (while CFP was cc'd). David to upgrade
mailman.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Still to do.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: See if N2478 changes anything for our proposals (which reference n2454).
See [Cfp-interest 1548] AI about newer C draft</span><br><span style=" font-size:10pt;font-family:sans-serif">
Good as is.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Get a paper number for CFP 1538 and submit it. See N2506: Range errors
and math functions</span><br><span style=" font-size:10pt;font-family:sans-serif">
Submitted as is. Nothing new.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get a paper number for the paper referenced in CFP 1516 and submit
it.</span><br><span style=" font-size:10pt;font-family:sans-serif">
See [Cfp-interest 1549] AI to submit paper about math function properties</span><br><span style=" font-size:10pt;font-family:sans-serif">
Submitted N2492.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Add in a note to CFP 1526 to say the cast raises no floating-point
exceptions.</span><br><span style=" font-size:10pt;font-family:sans-serif">
See [Cfp-interest 1550] AI to update note about INFINITY and NAN
macros and _Float16 </span><br><span style=" font-size:10pt;font-family:sans-serif">
David O: It looks compatible with C++.</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">
Proposal for short float, floating type extensions for C++ and C. Others?</span><br><span style=" font-size:10pt;font-family:sans-serif">
David O.: Short float was rejected in C++ two years ago. Don't want it
for C since C++ already said no. It is underspecified. Needs to be a specific
format and can't be a generic one.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2487: David O: Opposed to this.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: From IEEE's point of view, some have implemented it the
IEEE way and want it standardized. Machine learning evolving so rapidly
it is hard to say which is the most useful and so doubt there will be quick
consensus on the right format.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David O: There are 2 formats in the wild now, IEEE (1/5/10) and
bfloat16, 1 bit sign/8 bit exponent/7 bit mantissa. Next Nvidia chip will
support both formats in hardware. I want the same in the standard (2 separate
types with defined interactions).</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Block floats may be used too with a vector of integers (8 or 16
bit) with a single integer exponent field. The 754 email log on this is
on the 754 website.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David O: Just want to standardize existing practice and fit in new hardware
short floats into the existing framework.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: What determines critical mass to standardize?</span><br><span style=" font-size:10pt;font-family:sans-serif">
David O: Just want to have the framework so adding new types is easy and
rules are there for how it interacts with other types.</span><br><BR>