<span style=" font-size:10pt;font-family:sans-serif"> <b>Attendees</b>:
Rajan, Jim, Mike, Ian, David H.</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">
None.</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.</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">
Fred: Update erange proposal based on CFP 1437 and CFP teleconference discussion.
- Unknown.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Submit </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_NaN_and_infinity_macros_-_20191108.pdf to WG14. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Compile example code in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Choose how to attach footnote in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf; mention the other approach
in the problem description. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a paper proposing changing the “cr” prefix for correctly rounded
functions to “cr_”. Include with other suggested changes in response
to Jens’s naming paper. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Draft words to recommend honoring properties (Ex. even/odd, periodicity)
of math functions that would follow automatically from correct rounding.
- Not done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Find a place for words about math function properties. Coordinate
with David H (previous AI). - Not done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Comments:</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Monoticity as well and making correctly rounded
be recommended practice.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David: We can say if it is correctly rounded, they
get the properties anyways.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a proposal to change the return words for powr and add the footnote
(presented in the meeting) to justify powr. - 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: Look at seeing what would be involved in removing Annex J types that
already have the same basic types.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get a WG14 document number and submit C2x_proposal_-_why_no_wide_string_strfrom_functions-
20191230.pdf.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get a WG14 document number and submit C2x_proposal_-_names_and_locations-20200105.pdf.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ensure natural log is written as log in the standard (regarding C2x_proposal_-_powr_justification_wording-20200104.pdf).
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ensure thin spaces are put where needed in C2x_proposal_-_powr_justification_wording-20200104.pdf.
Ex. Between the e and y in the "e^y log x" in three places. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Update links on the C FP wiki to point to the latest drafts of the
TS parts and look into having a section for working drafts.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Ensure casting to _Float16 won't cause a problem with the using
INFINITY wherever a constant expression can be used change we proposed.</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, February 19th, 2020, 11:00 EST, 8:00 PST, 4PM UTC</span><br><span style=" font-size:10pt;font-family:sans-serif">
Same teleconference number.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Please notify the group if this time slot does not work.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim away Jan. 14-28th.</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">
754 revision:</span><br><span style=" font-size:10pt;font-family:sans-serif">
Done!</span><br><span style=" font-size:10pt;font-family:sans-serif">
CFP 1443 has the paper/article David wrote.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Drop this agenda item.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
C++ Liaison:</span><br><span style=" font-size:10pt;font-family:sans-serif">
Nothing.</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/n2433.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">):</span><br><span style=" font-size:10pt;font-family:sans-serif">
Draft with TS 1, 2, and 4a (Latest C2X draft: </span><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2454.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2454.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">,
also as link on CFP wiki)</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 3 - Was in a branch as work in progress prior to Jens stepping
down as editor. As Annex J.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 4b - Looking as an updated TS.</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">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
C2X target: 2023</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Idea is to propose IEEE 2019 binding in the next C meeting.
We can discuss next CFP meeting.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Question: Should we remove value redundant types from Annex
J? Ex. _Float32 being the same as float, _Float64 being the same as double,
_Float32x being the same as double or long double. We added this as consistency,
but the initial goal was just to provide nomenclature for the types.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Look at seeing what would be involved in removing
Annex J types that already have the same basic types.</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">
Fred: Update erange proposal based on CFP 1437 and CFP teleconference discussion.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Submit </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_NaN_and_infinity_macros_-_20191108.pdf to WG14. (</span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2469.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2469.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">)</span><br><span style=" font-size:10pt;font-family:sans-serif">
Looks good.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Compile example code in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf. (See Rajan’s CFP 1441)</span><br><span style=" font-size:10pt;font-family:sans-serif">
Looks good.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Choose how to attach footnote in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_why_no_wide_string_strfrom_functions_v2.pdf; mention the other approach
in the problem description. </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions-</span></a><span style=" font-size:10pt;font-family:sans-serif">20191230.pdf</span><br><span style=" font-size:10pt;font-family:sans-serif">
Looks good.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Get a WG14 document number and submit C2x_proposal_-_why_no_wide_string_strfrom_functions-
20191230.pdf.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a paper proposing changing the “cr” prefix for correctly rounded
functions to “cr_”. Include with other suggested changes in response
to Jens’s naming paper. </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_names_and_locations-20200105.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_names_and_locations-20200105.pdf</span></a><br><span style=" font-size:10pt;font-family:sans-serif">
cr_ was never proposed by any paper.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Moving the SNAN macros does follow the suggestion of renaming, but
also moves it which was not previously proposed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Get a WG14 document number and submit C2x_proposal_-_names_and_locations-20200105.pdf.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Draft words to recommend honoring properties of math functions
that would follow automatically from correct rounding.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Still to do.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Find a place for words about math function properties. Coordinate
with David H (previous AI).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Suggest adding a title to the table in F.3#23.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David: Functions that IEC 60559 recommends be correctly rounded</span><br><span style=" font-size:10pt;font-family:sans-serif">
David: The first table title should also be changed to distinguish
this table. Ex. Binding of operations required by IEC 60559; Binding of
functions or operations recommended by IEC 60559.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Or "Bindings of operations required by IEC 60559";
"Bindings of operations recommended by IEC 60559" See C FP 1453</span><br><span style=" font-size:10pt;font-family:sans-serif">
Suggest adding a second recommended practice to F.10.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a proposal to change the return words for powr and add the footnote
(presented in the meeting) to justify powr. </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_powr_justification_wording-20200104.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_powr_justification_wording-20200104.pdf</span></a><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Ensure natural log is written as log in the standard
(regarding C2x_proposal_-_powr_justification_wording-20200104.pdf). </span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Ensure thin spaces are put where needed in C2x_proposal_-_powr_justification_wording-20200104.pdf.
Ex. Between the e and y in the "e^y log x" in three places. </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">
WG14 editor change</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim and Rajan meeting with David Keaton regarding finishing off
the work.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Is “Floating-point extensions for C” still an appropriate description
of CFP work? See Mike’s email CFP 1445.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: "IEC 60559 Floating point support in C"?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Sounds good.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Also remove reference to 2008 on the website.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Update links to the published TS's on the website.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Link published for all, and have working drafts for
any ones with changes or that are not in C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Update links on the C FP wiki to point to the latest
drafts of the TS parts and look into having a section for working drafts.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Issue for _Float16: INFINITY has type float so widens operations with _Float16
operands.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ideally NAN and INFINITY macros would be _Float16 if it was
supported. We could add a comment suggesting putting a cast to _Float16
in front of INFINITY if you really wanted operations to stay in _Float16
type.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Doesn't work for SNAN's.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Not an issue since we have type'd versions of those.</span><br><span style=" font-size:10pt;font-family:sans-serif">
May be an issue for constant expressions.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Rajan: Ensure casting to _Float16 won't cause a problem
with the using INFINITY wherever a constant expression can be used change
we proposed.</span><br><BR>