<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Fred,
Mike, David H.</font><br><br><font size=2 face="sans-serif"><b> New agenda items:</b></font><br><font size=2 face="sans-serif"> NaNQ and NaNS as output
from printf functions for quite and signaling nans respectively</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"> 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"><b> Last meeting action items:</b></font><br><font size=2 face="sans-serif"> Jim: Remove screen-share
information from the agenda. - Not Done.</font><br><font size=2 face="sans-serif"> Jim: Missing line numbers
for part 2 (cfp2x-20180612.pdf) - Done (for all parts).</font><br><font size=2 face="sans-serif"> Jim: Specification for
inexact: Make the editorial change as given in the modified agenda with
links. - Done.</font><br><font size=2 face="sans-serif"> Fred: Fix the wording
for CR21 to specify odd significand. - Done.</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. - Done.</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. - Done.</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). - Done.</font><br><font size=2 face="sans-serif"> Jim: Create a paper/proposal
for the loosening of the totalorder* specifications to match 754-201x.
- Done (email sent why to not do this).</font><br><font size=2 face="sans-serif"> Fred: Recheck 'Functions
and infinity' issues with 754 draft 238. - Not done (now draft 240).</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). - Done.</font><br><font size=2 face="sans-serif"> Jim: Create a CR to change
the reduction operations description from should->shall. - Done (email
sent why not to do this).</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"> David H: Check the new
specification for inexact (action item 1) to make sure the new words still
work with 754.</font><br><font size=2 face="sans-serif"> Rajan: Bring a proposal
forward for NaNQ and NaNS printf output to this group next meeting.</font><br><font size=2 face="sans-serif"> Fred: Look into reduction
functions and NaN's for optional exceptions.</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"> Tuesday, August 28th 2018,
11:00 EDT, 8:00 PDT, 3PM UTC</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"> Approved draft
240. Going to sponsor ballot. Unanimous.</font><br><font size=2 face="sans-serif"> Some issues still
open that people may raise in the ballot.</font><br><font size=2 face="sans-serif"> May need changes
to formatting and templates.</font><br><font size=2 face="sans-serif"> Deadline to register
to be on the ballot body: At least a month away.</font><br><font size=2 face="sans-serif"> May be some issues
with ISO, ANSI, etc. but not sure.</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"> </font><br><font size=2 face="sans-serif"> Action item details (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda-20180725-links.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda-20180725-links.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Specification for
inexact (Jim’s 6/26 email “AI about specification for inexact”):</font><br><font size=2 face="sans-serif"> Suggested
different change – not in cfp4x yet</font><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> David H:
Check to make sure this still works with 754.</font><br><font size=2 face="sans-serif"> Wording for CR21
to specify odd significand (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180707.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180707.pdf</font></a><font size=2 face="sans-serif">,
page 18):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> C support for 754-201x.
N document numbers for 9.5 and 9.6 additions (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2275.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2275.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> David: No
longer expect additions.</font><br><font size=2 face="sans-serif"> Looks good
as is. Rajan to mention no additions expected.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Min/max C specification
matches IEEE? (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2273.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2273.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> Keep as
a proposal.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Augmented* C function
specifications match IEEE? (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2274.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2274.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> If asked
what to do in the future, the group is OK with updating the TS's after
C2X to rebase any remaining TS's to C2X and IEEE 754-2018.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> C in cfp1x </font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180707.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180707.pdf</font></a><font size=2 face="sans-serif">page 30 (N2272: </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2272.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2272.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Loosening of the
totalorder* specifications in 754-201x (Jim’s 6/27 email “AI about change
to totalorder”):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><br><font size=2 face="sans-serif"> 'Functions and
infinity' issues with 754 draft 238.</font><br><font size=2 face="sans-serif"> Leave until
next meeting.</font><br><br><font size=2 face="sans-serif"> CR to change CFP
to say for Annex F of C that pow(+/-0,-inf) has no exception (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2271.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2271.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Looks good.</font><br><br><font size=2 face="sans-serif"> CR to change the
reduction operations description from should->shall (Jim’s 6/28 email
“AI about reduction requirements”):</font><br><font size=2 face="sans-serif"> Fred: Should
we say it should not raise exceptions?</font><br><font size=2 face="sans-serif"> Jim:
No, since we don't say what it can't do in general. We are doing what 754
says in terms of NaN gives NaN.</font><br><font size=2 face="sans-serif"> Looks good.</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"> Joseph Myers 7/19,20
email “Better than _Either(A, B)* (SC22WG14.15433, SC22WG14.15435, SC22WG14.15437)</font><br><font size=2 face="sans-serif"> Rajan: First
message was in response to 15388.</font><br><font size=2 face="sans-serif"> Fred: Another
proposal 15438.</font><br><font size=2 face="sans-serif"> C FP response:
The group heartily endorses Joseph's position on this topic.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> NaNQ/NaNS proposal:</font><br><font size=2 face="sans-serif"> Look at
current 754 draft to see if NaNQ/NaNS violates it.</font><br><font size=2 face="sans-serif"> Also look
at the current C with TS's and see if is still valid there.</font><br><font size=2 face="sans-serif"> Rajan: Bring
proposal forward for NaNQ and NaNS printf output to this group next meeting</font><br><br><font size=2 face="sans-serif"> C2X Integration:</font><br><font size=2 face="sans-serif"> Mailing deadline
in September.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Activities in progress:</font><br><font size=2 face="sans-serif"> </font><br><br><font size=2 face="sans-serif"> Deferred issues:</font><br><font size=2 face="sans-serif"> </font><br><BR>