<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, 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"> Jim: Update activities
list. - Done.</font><br><font size=2 face="sans-serif"> Fred: See where we are
for inconsistent spec for infinities</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: Look at what is said
in exception handling and make sure remainder underflow is addressed as
per Jim's/Fred/David's email regarding 18661-1 and 754 (2018/04/09). -
Done.</font><br><font size=2 face="sans-serif"> Jim: 754 compatibility:
roundeven: Put in the parenthetical (conclusion) into part 1 as per Jim's
response to David on the 2018/04/09 email. - Done.</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"> David: Evaluate the 18661-4
tanpi and ensure it is not a bad idea. Also ask 754 what we (CFP) should
do with it. - Done. 754 will incorporate the C specification.</font><br><font size=2 face="sans-serif"> All: Look at Fred's 2018/02/19
email titled "18661-2 and 754". - Done.</font><br><font size=2 face="sans-serif"> Jim: Integrate the 2018/04/05
DR13 change into N2213 and get a new N document so we can talk to that
in WG14. - Done.</font><br><font size=2 face="sans-serif"> Jim: Part 4: Change the
exp10m1 description to allow underflow range errors. - 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"> Rajan: Give a valid version
of C17 to Jim for posting on CFP.</font><br><font size=2 face="sans-serif"> Jim: Ask Blaine about
missing references to DECIMAL_DIG (only one found was the example).</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.</font><br><font size=2 face="sans-serif"> Jim: Create a CR for llquantexp
with the fix in Jim's 2018/05/12 note.</font><br><font size=2 face="sans-serif"> Jim: Review specification
for raising the inexact exception in the TS's.</font><br><font size=2 face="sans-serif"> Jim: Put CR21 on the agenda
for next time.</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.</font><br><font size=2 face="sans-serif"> Rajan: Reply to Joseph's
note and ask for any particular concerns.</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"> <b>Wednesday</b>, June
20th 2018, 11:00 EDT, 8:00 PDT</font><br><font size=2 face="sans-serif"> *<b>Note</b>:* New time
and day: 1h earlier, Wednesday.</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"> WG14:</font><br><font size=2 face="sans-serif"> *Rajan: Give a
valid version of C17 to Jim for posting on CFP.</font><br><font size=2 face="sans-serif"> Meeting summary:</font><br><font size=2 face="sans-serif"> Jim: Ask
Blaine about missing references to DECIMAL_DIG (only one found was the
example).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> IEEE 754 revision:</font><br><font size=2 face="sans-serif"> tanpi is cloned
from C to 754.</font><br><font size=2 face="sans-serif"> Dealing with minor
issues.</font><br><font size=2 face="sans-serif"> Ex. Wording
issues.</font><br><font size=2 face="sans-serif"> Likely to get a
draft this year, but likely to be published in 2019.</font><br><font size=2 face="sans-serif"> Meeting at the
ARITH conference in June.</font><br><font size=2 face="sans-serif"> Need to know when
it is going to be an international standard.</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><br><font size=2 face="sans-serif"> Exception Handling
and remainder underflow (Jim's May 8th email: AI about remainder underflow):</font><br><font size=2 face="sans-serif"> David: Without
alternate exception handling, you wouldn't even know about it.</font><br><font size=2 face="sans-serif">
</font><br><font size=2 face="sans-serif"> Editorial change
for roundeven in part 1 (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180509.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp1x-20180509.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"> Min/max C specification
matches IEEE? (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/min-max_spec20180310.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/min-max_spec20180310.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Leave for
next meeting.</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/augop_spec-20180311.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/augop_spec-20180311.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Leave for
next meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> 754 input about
whether to keep tanpi</font><br><font size=2 face="sans-serif"> Jim: In
the binding table. Need to add in the acospi, etc. into the Part 4 binding
table.</font><br><font size=2 face="sans-serif"> David: Not
in 2018 draft.</font><br><font size=2 face="sans-serif"> Jim: They
should to into the 202X draft.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Fred's 2018/02/19
email "18661-2 and 754" (Email thread 4/10-5/16)</font><br><font size=2 face="sans-serif"> Jim's 5-12-2018
note:</font><br><font size=2 face="sans-serif"> The
general statement for canonical results unless otherwise specified seems
good.</font><br><font size=2 face="sans-serif"> quantize:
We should add it.</font><br><font size=2 face="sans-serif"> *Jim:
Make the quantize and general canonical results changes as editorial changes
for part 2</font><br><font size=2 face="sans-serif"> llquantexp:
Is it an editorial change? Not in 754 2008.</font><br><font size=2 face="sans-serif">
Jim: Need to add it to the binding table too.</font><br><font size=2 face="sans-serif">
Jim: Not a binding issue.</font><br><font size=2 face="sans-serif"> The bit
operations can give non-canonical results. No discussion of the sign bit.
IEEE will look at that.</font><br><font size=2 face="sans-serif"> The sign-bit
operations can propagate non-canonical results.</font><br><font size=2 face="sans-serif"> For Part
1, list the exceptions to the canonical expectation.</font><br><font size=2 face="sans-serif"> List
copy as propagate non-canonical results. Other functions like that might
return non-canonical results given non-canonical inputs.</font><br><font size=2 face="sans-serif"> We
should just list the most you can say as to the result and let the implementations
deal with it.</font><br><font size=2 face="sans-serif">
Jim: Who would we hurt if we asked for it to be canonicalized?</font><br><font size=2 face="sans-serif">
David: For sign-magnitude encodings.</font><br><font size=2 face="sans-serif">
Jim: We can say it is intended to allow bit operations for interchange
types and extended types if the encodings permit.</font><br><font size=2 face="sans-serif">
See what 754 says.</font><br><font size=2 face="sans-serif"> For
C, where do we list the exceptions to canonical results? Do we say it for
each of the operations?</font><br><font size=2 face="sans-serif">
Similar question for the inexact exception.</font><br><font size=2 face="sans-serif">
Jim: Suggestion: For parts 1, 2: Say they raise inexact iff the result
is inexact. For part 4 say they should raise inexact iff the result is
inexact. For augmented, say raise underflow/overflow but not otherwise.</font><br><font size=2 face="sans-serif">
*Jim: Review specification for raising the inexact exception in the TS's</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> 2018/04/05 C R13
change and N2213 (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2252.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2252.pdf</font></a><font size=2 face="sans-serif">)</font><br><font size=2 face="sans-serif"> Missing
final parenthesis at the end of the document.</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"> Change for exp10m1
to allow underflow range errors (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp4x-20180516.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp4x-20180516.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"> Consistency for
infinities</font><br><font size=2 face="sans-serif"> Leave for
next meeting.</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"> From WG14: CFP
to come back with: a new suggested C11-only change based on CFP DR20 for
C DR501; and TS-only changes in CFP DR20</font><br><font size=2 face="sans-serif"> </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2253.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2253.pdf</font></a><br><font size=2 face="sans-serif"> C
changes.</font><br><font size=2 face="sans-serif"> Jim:
Only saw one DECIMAL_DIG that was missed (at end of page 1).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2254.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2254.pdf</font></a><br><font size=2 face="sans-serif"> Part
1 changes.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2255.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2255.pdf</font></a><br><font size=2 face="sans-serif"> Part
3 changes.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Note there
are cleanup changes as well, not just DECIMAL_DIG removals.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> CR21: Seems OK.
Not sure why the change was made to the exponents.</font><br><font size=2 face="sans-serif"> *AI: Jim:
Put CR21 on the agenda for next time.</font><br><font size=2 face="sans-serif"> Jim: Not
sure why we say odd numbers instead of significand as odd.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> WG14 process for
CFP CR's:</font><br><font size=2 face="sans-serif"> Create a
new N document for each new CR with a suggested TC.</font><br><font size=2 face="sans-serif"> For updating
an existing CR, submit a new N document with the suggested TC.</font><br><font size=2 face="sans-serif"> Each CR
should update one part of the TS or for C. If it affects multiple parts,
they should be separate CR's.</font><br><font size=2 face="sans-serif"> Send Blaine
HTML for each new or updated CR.</font><br><font size=2 face="sans-serif"> Blaine creates
the compendium.</font><br><font size=2 face="sans-serif"> WG14 votes
on moving the CR's forward.</font><br><font size=2 face="sans-serif">
</font><br><font size=2 face="sans-serif"> Binding for IEEE 754-2018:</font><br><font size=2 face="sans-serif"> WG14 paper about
updating to IEEE 754:2018 (</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">):</font><br><font size=2 face="sans-serif"> Rajan: 9.7:
What is the CR needed?</font><br><font size=2 face="sans-serif"> Jim:
The functions are not in the binding table.</font><br><font size=2 face="sans-serif"> Most references
to IEC 60559 2011 do not show up in C, so updating the TS's for the new
60559 publish year will need to be made.</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</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Functions for augmented
arithmetic</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Min/max functions</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Payload functions</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Total order functions</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> C2X integration:</font><br><font size=2 face="sans-serif"> Joseph Myers sent
an email (15205) saying to listen to implementation experience when adding
the TS's to C2X.</font><br><font size=2 face="sans-serif"> *AI: Rajan:
Reply to Joseph's note and ask for any particular concerns.</font><br><font size=2 face="sans-serif"> Can use
that to update our proposal implementation experience sections.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Activities (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180521.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180521.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> </font><a href="http://wiki.edg.com/pub/CFP/WebHome/Defect_reports_-_TS_18661-20180519.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/Defect_reports_-_TS_18661-20180519.pdf</font></a><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Deferred issues:</font><br><font size=2 face="sans-serif"> C standard use
of "floating" vs "floating-point":</font><br><font size=2 face="sans-serif"> Delay until
later.</font><br><font size=2 face="sans-serif"> </font><BR>