<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Ian,
Fred, David H.</font><br><br><font size=2 face="sans-serif"><b> New agenda items:</b></font><br><font size=2 face="sans-serif"> None</font><br><br><font size=2 face="sans-serif"><b> Carry over action items:</b></font><br><font size=2 face="sans-serif"> Ian: See if there is an
incompatibility between C and C++ for constants being evaluated to a wider
format (Ex. FLT_EVAL_METHOD affects constants in C++, and wider return
values) - Keep open (Hubert: Not defined and left up to C)</font><br><font size=2 face="sans-serif"> Jim: Update the binding
table in parts 1 and 2 to handle the new IEEE-754:2018 functions when published.
- Keep open.</font><br><font size=2 face="sans-serif"> Fred: See where we are
for inconsistent spec for infinities - Done.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"><b> Last meeting action items:</b></font><br><font size=2 face="sans-serif"> David: Check the min/max
C specification to ensure it matches what IEEE has. - Not done.</font><br><font size=2 face="sans-serif"> David: Check the augmented*
C function specifications to ensure they match what IEEE has. - Not done.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Rajan: Give a valid version
of C17 to Jim for posting on CFP. - Done.</font><br><font size=2 face="sans-serif"> Jim: Ask Blaine about
missing references to DECIMAL_DIG (only one found was the example). - Done.</font><br><font size=2 face="sans-serif"> Jim: Make the quantize
and general canonical results changes as editorial changes for part 2 as
per Jim's 2018/05/12 note. - Done.</font><br><font size=2 face="sans-serif"> Jim: Create a CR for llquantexp
with the fix in Jim's 2018/05/12 note. - Done.</font><br><font size=2 face="sans-serif"> Jim: Review specification
for raising the inexact exception in the TS's. - Done.</font><br><font size=2 face="sans-serif"> Jim: Put CR21 on the agenda
for next time. - Done.</font><br><font size=2 face="sans-serif"> Jim: Get N documents for
the features mentioned in </font><a href="http://wiki.edg.com/pub/CFP/WebHome/C_support_for_754-201x-20180518.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C_support_for_754-201x-20180518.pdf</font></a><font size=2 face="sans-serif">and use this as new document for Pittsburgh. - Done.</font><br><font size=2 face="sans-serif"> Rajan: Reply to Joseph's
note and ask for any particular concerns. - Done.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"><b> New action items:</b></font><br><font size=2 face="sans-serif"> Jim: Remove screen-share
information from the agenda.</font><br><font size=2 face="sans-serif"> Jim: Missing line numbers
for part 2 (cfp2x-20180612.pdf)</font><br><font size=2 face="sans-serif"> Jim: Specification for
inexact: Make the editorial change as given in the modified agenda with
links.</font><br><font size=2 face="sans-serif"> Fred: Fix the wording
for CR21 to specify odd significand.</font><br><font size=2 face="sans-serif"> Jim: C support for 754-201x:
Say as per current IEEE draft and add in the N document numbers for 9.5
and 9.6 additions.</font><br><font size=2 face="sans-serif"> Jim: Submit the augmented
arithmetic and min/max spec for 754:201x binding proposals to WG14 after
removing change marks.</font><br><font size=2 face="sans-serif"> Jim: Create a CR for changing
"not infinite" to "finite" as per the description for
remainder (18661-1, F.10.7.2).</font><br><font size=2 face="sans-serif"> Jim: Create a paper/proposal
for the loosening of the totalorder* specifications to match 754-201x.</font><br><font size=2 face="sans-serif"> Fred: Recheck 'Functions
and infinity' issues with 754 draft 238.</font><br><font size=2 face="sans-serif"> Jim: Create a CR to change
CFP to say for Annex F of C that pow(+/-0,-inf) has no exception (i.e.
Remove the latitude to raise div-by-zero).</font><br><font size=2 face="sans-serif"> Jim: Create a CR to change
the reduction operations description from should->shall</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"><b> Next Meeting(s):</b></font><br><font size=2 face="sans-serif"> Wednesday, July 25th 2018,
11:00 EDT, 8:00 PDT</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Same teleconference number.</font><br><br><font size=2 face="sans-serif"><b> Discussion:</b></font><br><font size=2 face="sans-serif"> IEEE 754 revision:</font><br><font size=2 face="sans-serif"> David: Finding
more things that are incorrect or inconsistent.</font><br><font size=2 face="sans-serif"> Various
contributions from the C FP group (this group).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> C++ liaison:</font><br><font size=2 face="sans-serif"> Nothing.</font><br><font size=2 face="sans-serif"> Ian: Looking into
getting a connection with the C++ committee.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Action item details (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda_20180621-links.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda_20180621-links.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> quantize and canonical
results changes for part 2 (and part 1):</font><br><font size=2 face="sans-serif"> Fred: Since
these are changes to the main body of the standard other than an annex
it is not good.</font><br><font size=2 face="sans-serif"> Jim: Since
Decimal can only be 754 it doesn't need to be in Annex F.</font><br><font size=2 face="sans-serif"> Fred: It
should mention domain error as well as invalid.</font><br><font size=2 face="sans-serif"> Jim:
It does.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> llquantexp:</font><br><font size=2 face="sans-serif"> Since it
is not a 754 function, we need a CR. It has been submitted. Blaine should
assign a CR number for this.</font><br><font size=2 face="sans-serif"> Missing
line numbers in part 2.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Specification for
inexact:</font><br><font size=2 face="sans-serif"> Fred: Should
overflow and underflow be in quotes as well?</font><br><font size=2 face="sans-serif"> Jim:
Considering them as conditions.</font><br><font size=2 face="sans-serif"> David:
underflow could be exact so don't need to raise the inexact exception.</font><br><font size=2 face="sans-serif"> Consider
this as an editorial change.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> CR21:</font><br><font size=2 face="sans-serif"> Jim: It
is for the significand being odd. We should say that.</font><br><font size=2 face="sans-serif"> David:
Perhaps say when both the significands are odd?</font><br><font size=2 face="sans-serif"> Jim:
Yes, a little strange though since significands are usually expressed as
fractions.</font><br><font size=2 face="sans-serif"> Jim:
both choices are odd -> both choices have an odd least significand digit,
and similar for the end of the last line.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> N docs for 754-201x
support:</font><br><font size=2 face="sans-serif"> Jim: Got
the N numbers.</font><br><font size=2 face="sans-serif"> Added tanpi
to the list.</font><br><font size=2 face="sans-serif"> Need to
say as per current IEEE draft.</font><br><font size=2 face="sans-serif"> Need to
add in the N document numbers for 9.5 and 9.6 additions.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Augmented arithmetic:</font><br><font size=2 face="sans-serif"> Jim: Added
in the invalid exception for augadd, augsub</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> min/max spec:</font><br><font size=2 face="sans-serif"> Jim: Added
in part 3 changes.</font><br><font size=2 face="sans-serif"> This is
a proposal for changes for TS's 1-3, not a CR. It is at the same time as
support for the next version of the 754 standard.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Consistency for
infinities (note chain titled Functions and infinity):</font><br><font size=2 face="sans-serif"> Changing
not infinite to finite as per the description for remainder.</font><br><font size=2 face="sans-serif"> totalorder*:
Now up to the implementation on how to order them done on purpose by 754.
Should make this a paper for a new feature/change, not a CR.</font><br><font size=2 face="sans-serif"> Although
we wish we had originally had NaN refer to both quiet and signalling, it
is too much of a change now (with the potential of missing areas or having
errors) so we will not do it.</font><br><font size=2 face="sans-serif"> rootn(1,
0): To match pow, rootn(1, 0) should give 1.</font><br><font size=2 face="sans-serif"> David:
In 754:2008, n = 0 is invalid for rootn so changing that would be a substantive
change.</font><br><font size=2 face="sans-serif">
If something changes, it would have to be in 754.</font><br><font size=2 face="sans-serif"> rootn(inf,
n) missing in 754:</font><br><font size=2 face="sans-serif"> David:
Added in the latest 754 draft 238.</font><br><font size=2 face="sans-serif"> pow(0,-inf):</font><br><font size=2 face="sans-serif"> Change
CFP to match 754. New CR.</font><br><font size=2 face="sans-serif"> powr:</font><br><font size=2 face="sans-serif"> David:
The whole idea of these functions was to simplify exception processing.</font><br><font size=2 face="sans-serif">
Problematic for which sub-exceptions should be signalled.</font><br><font size=2 face="sans-serif"> David:
CFP shouldn't change since the same problem for both 754 and CFP.</font><br><font size=2 face="sans-serif"> reduction
operations need should -> shall.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Other issues:</font><br><font size=2 face="sans-serif"> None.</font><BR>