<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Fred,
Mike, Ian (late entry)</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> Last meeting 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"> All: Look into why the
cbrt macro (DR16) has the parameters inside the generic selection.</font><br><font size=2 face="sans-serif"> Jim: Re-update activities
list. - Done.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Rajan: Ask Ian if he knows
of someone who can take over the C++ liaison role for him. - Done: Ian
may be continuing, no backup that he knows of.</font><br><font size=2 face="sans-serif"> Unassigned: C footnote
232 uses the extraordinary roundoff error aspect from IEEE that was taken
out in the IEEE 2008 draft. Fix this? - Done.</font><br><font size=2 face="sans-serif"> Jim: Add in part of the
note for the pow function in part 1 somewhere as a change to F.3 to restate
that the specifications should match IEC 60559. - Done.</font><br><font size=2 face="sans-serif"> Jim: Get a DR against
part 4 for </font><a href=http://wiki.edg.com/pub/CFP/WebHome/DR_for_missing_specification_of_preferred_quantum_exponents.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/DR_for_missing_specification_of_preferred_quantum_exponents.pdf</font></a><font size=2 face="sans-serif">.
- Done (DR18, N2204).</font><br><font size=2 face="sans-serif"> Fred: Put the words for
the roundTiesToEven with a change to Annex F as a part 1 DR as per his
note on 2018/02/18 with the change of "which could produce" ->
"whose nearest neighbors are". - Not done.</font><br><font size=2 face="sans-serif"> Jim: </font><a href=http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG.pdf:><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG.pdf:</font></a><font size=2 face="sans-serif">Make the changes to the type_ to reflect the FLT, DBL and LDBL prefixes.
- Done (2018/02/21 email, replaced by 2018/03/06 email).</font><br><font size=2 face="sans-serif"> Jim: TS DR15 (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/DR_for_macros_for_non-arith_formats-20180211.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/DR_for_macros_for_non-arith_formats-20180211.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Change "Suggested"
to "Proposed", "into a proposed" -> "as is
into a proposed" - Done.</font><br><font size=2 face="sans-serif"> Fred, Rajan: Check if
the _Generic replacement suppress macro expansion. - Done (no suppression).</font><br><font size=2 face="sans-serif"> Jim: Get a new N document
for the new proposed TC for TS DR16. - Done.</font><br><font size=2 face="sans-serif"> Jim: Write up the TS DR13
2018/02/18 Jim's email as a suggested TC. - Done.</font><br><font size=2 face="sans-serif"> David: Look into the IEEE
binding differences to see if they are real issues (from Fred's email on
2018/02/18). - Not 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: Create a DR against
part 1 for updating C footnote 232 as per emails on 2018/02/22.</font><br><font size=2 face="sans-serif"> Jim: Obsolescing DECIMAL_DIG
(</font><a href="http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf</font></a><font size=2 face="sans-serif">):
Change 1: Change "decimal" to "decimal character sequence"
throughout the document to avoid confusion with DFP. Also need to qualify
it with the rounding mode.</font><br><font size=2 face="sans-serif"> Jim: Obsolescing DECIMAL_DIG
(</font><a href="http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf</font></a><font size=2 face="sans-serif">):
Change TS 18661-1 10.1: Needs the round to nearest rounding mode text as
per the previous action item.</font><br><font size=2 face="sans-serif"> Jim: Obsolescing DECIMAL_DIG
(</font><a href="http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf</font></a><font size=2 face="sans-serif">):
Change TS 18661-1 10.1: Typo: IEC 60669 -> IEC 60559</font><br><font size=2 face="sans-serif"> Jim: Obsolescing DECIMAL_DIG
(</font><a href="http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/changes_for_obsolescing_DECIMAL_DIG-20180306.pdf</font></a><font size=2 face="sans-serif">):
Get a document number and submit in time for the mailing if possible.</font><br><font size=2 face="sans-serif"> Jim: TS DR16: Remove the
cbrt examples in parts 2 and 3 for cbrt as part of DR16 as a note for an
editorial change.</font><br><font size=2 face="sans-serif"> Jim: TS DR13: </font><a href="http://wiki.edg.com/pub/CFP/WebHome/Re-revised_suggested_TC_for_CFP_DR_13-20180223.pdf:"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/Re-revised_suggested_TC_for_CFP_DR_13-20180223.pdf:</font></a><font size=2 face="sans-serif">Send it out (with fixes to the font/alignment).</font><br><font size=2 face="sans-serif"> Jim: Reword </font><a href="http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf</font></a><font size=2 face="sans-serif">F.10.13 description to say something along the lines of "a floating
point number with an unsigned integer value" and for the function
descriptions as well.</font><br><font size=2 face="sans-serif"> Fred: </font><a href="http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180313.pdf:"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180313.pdf:</font></a><font size=2 face="sans-serif">See where we are for inconsistent spec for infinities.</font><br><font size=2 face="sans-serif"> Fred: </font><a href="http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180313.pdf:"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180313.pdf:</font></a><font size=2 face="sans-serif">See where we are for missing Annex F spec for new functions.</font><br><font size=2 face="sans-serif"> Jim: Working drafts: Try
red strike-through for parts 2-5 and red caret for part 1.</font><br><br><font size=2 face="sans-serif"><b> Next Meetings:</b></font><br><font size=2 face="sans-serif"> Tuesday April 10th 2018,
12:00 EDT, 9:00 PST</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"> Working drafts of the
TS's:</font><br><font size=2 face="sans-serif"> Seems helpful.</font><br><font size=2 face="sans-serif"> Posted. Links on
the CFP homepage to the working drafts.</font><br><font size=2 face="sans-serif"> Since not
DIS based, can distribute freely.</font><br><font size=2 face="sans-serif"> Jim: Try red strike-through
for parts 2-5 and caret for part 1.</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"> C Footnote 232
(extraordinary roundoff): As per emails around 2018/02/22</font><br><font size=2 face="sans-serif"> Fred: Applies
to even exact small values.</font><br><font size=2 face="sans-serif"> Jim:
Yes. But remember range errors are allowed but not required.</font><br><font size=2 face="sans-serif"> Jim: Should
be a DR against part 1. Can be against C but part 1 made it worse.</font><br><font size=2 face="sans-serif"> *Jim: Create
a DR against part 1 for updating C footnote 232 as per emails on 2018/02/22.</font><br><font size=2 face="sans-serif"> Note: This
change is not in the working drafts yet.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Note for consistency
with IEC 60559: </font><br><font size=2 face="sans-serif"> Editorial
change.</font><br><font size=2 face="sans-serif"> Present
in the working drafts.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> DR about roundTiesToEven:
</font><br><font size=2 face="sans-serif"> Fred: Upcoming
before next meeting as Fred will not be present for the next meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Changes for obsolescing
DECIMAL_DIG: As per 2018/03/06 email from Jim</font><br><font size=2 face="sans-serif"> First Change:</font><br><font size=2 face="sans-serif"> *Jim:
Change "decimal" to "decimal character sequence" to
avoid confusion with DFP throughout the document.</font><br><font size=2 face="sans-serif"> *Jim:
This change should say it should be roundToNearest to keep the identity
function.</font><br><font size=2 face="sans-serif"> Change:
C11 F.5</font><br><font size=2 face="sans-serif"> Note
that the part 1 change will supersede this change.</font><br><font size=2 face="sans-serif"> Change:
TS 18661-1 10.1</font><br><font size=2 face="sans-serif"> *Also
needs the round to nearest rounding mode.</font><br><font size=2 face="sans-serif"> *Need
to correct IEC 60669 -> IEC 60559</font><br><font size=2 face="sans-serif"> Attempt
to get this in by the WG14 mailing (March 26th deadline) for the next WG14
meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> New TC for TS DR16
(cbrt): </font><br><font size=2 face="sans-serif"> Fred/Rajan:
Better to drop the examples from part 2 and 3.</font><br><font size=2 face="sans-serif"> Jim: We
should say something along the lines of "if the supported types are
float, double, and long double"</font><br><font size=2 face="sans-serif"> Rajan:
Since this is an example, and non-normative, we should just leave it as
is.</font><br><font size=2 face="sans-serif"> *Jim: Remove
the examples in parts 2 and 3 for cbrt as part of DR16 as a note for an
editorial change.</font><br><font size=2 face="sans-serif"> The part
1 change is a part of the working drafts.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> TS DR 13 (type
generic for narrower type: </font><a href="http://wiki.edg.com/pub/CFP/WebHome/Re-revised_suggested_TC_for_CFP_DR_13-20180223.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/Re-revised_suggested_TC_for_CFP_DR_13-20180223.pdf</font></a><font size=2 face="sans-serif">):
</font><br><font size=2 face="sans-serif"> Font and
alignment changes have been fixed.</font><br><font size=2 face="sans-serif"> *Jim: Get
a document number and send it out.</font><br><font size=2 face="sans-serif"> </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"> </font><br><br><font size=2 face="sans-serif"> C++ liaison:</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Issues:</font><br><font size=2 face="sans-serif"> Does CR_DECIMAL_DIG
have the same issues as DECIMAL_DIG?</font><br><font size=2 face="sans-serif"> Jim: No,
since it is a new macro and not changing anything that is already present.</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"> </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"> Need an updated
list of changes in IEEE.</font><br><font size=2 face="sans-serif"> Jim to talk
to David H. to get this.</font><br><font size=2 face="sans-serif"> </font><a href="http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf:"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf:</font></a><br><font size=2 face="sans-serif"> Changes
are compared to part 1.</font><br><font size=2 face="sans-serif"> Trying to
align to what 754 has regarding payloads.</font><br><font size=2 face="sans-serif"> Rajan: Saying
unsigned integer at the start and then "sign of the returned integer
is positive" mismatch.</font><br><font size=2 face="sans-serif"> Mike: Say
a floating point number with an unsigned integer value in the main description?</font><br><font size=2 face="sans-serif"> *Jim: Reword
</font><a href="http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/NaN_payload_functions_for_C-20180311.pdf</font></a><font size=2 face="sans-serif">F.10.13 description to say something along the lines of "a floating
point number with an unsigned integer value"</font><br><font size=2 face="sans-serif"> Rajan:
Apply the change to the function descriptions too.</font><br><font size=2 face="sans-serif"> </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><br><font size=2 face="sans-serif"> Looks good.</font><br><font size=2 face="sans-serif"> </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><br><font size=2 face="sans-serif"> Looks good.</font><br><br><font size=2 face="sans-serif"> C2X integration:</font><br><font size=2 face="sans-serif"> </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-20180313.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20180313.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Obsolesce Decimal_dig
will have a paper number soon.</font><br><font size=2 face="sans-serif"> Working on process
for defects still with Blaine and David K.</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"> *Fred: See where
we are for missing Annex F spec for new functions.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> C Standard use of "Floating"
vs "Floating-point":</font><br><font size=2 face="sans-serif"> </font><BR>