<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Ian, Jim,
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"> 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.</font><br><font size=2 face="sans-serif"> Seems to be incompatible
in the older C++ standard. Ex. C++ did not allow evaluation in a greater
precision than the type.</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. - Done.</font><br><font size=2 face="sans-serif"> David: Check the augmented*
C function specifications to ensure they match what IEEE has. - Done.</font><br><font size=2 face="sans-serif"> All: totalorder* differ
for NaN payloads: Note that we don’t have approval to move up to 754 201x
yet. - Keep open: Revisit after we move up to the 754 draft.</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: Post the draft of
Part 1 integrated into C2x on the CFP site. - Done.</font><br><font size=2 face="sans-serif"> Jim: Make the first change
as per CFP1238. - Done.</font><br><font size=2 face="sans-serif"> Jim: Rework Part 3 as
an Annex to add a note saying there is no _Decimal32x since IEC60559 doesn't
have _Decimal32 as a basic type. - Done.</font><br><font size=2 face="sans-serif"> Jim: Make the _EPSILON
change as per CFP1238. - Done.</font><br><font size=2 face="sans-serif"> Jim: Make the forth change
as per CFP1238 to add in the hyperbolic versions of cos/sin/tan. - Done.</font><br><font size=2 face="sans-serif"> Jim: Make the fifth change
as per CFP1238 for the list changes. - Done.</font><br><font size=2 face="sans-serif"> All: Take a look at part
3 annex (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20190119.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20190119.pdf</font></a><font size=2 face="sans-serif">)
draft before next meeting. - Done.</font><br><font size=2 face="sans-serif"> Jim: Update the proposal
to try again to integrate part 4a into C2X. - Done.</font><br><font size=2 face="sans-serif"> David: Check with IEEE
group to see if there is any implementations for Part 4b functions (hardware
or software). - Done.</font><br><font size=2 face="sans-serif"> All: Review the rationale
for part 5 a, b, c proposal. - Carry over.</font><br><font size=2 face="sans-serif"> All: Review </font><a href=http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf</font></a><font size=2 face="sans-serif">.
- Done.</font><br><font size=2 face="sans-serif"> Rajan: Say to WG14 that
CFP supports removing the WANT macros and leaving the rest as is due to
Fred's reasoning. - Carry over. Note: Also mention CFP's appreciation to
Jens for the integration editing (done really well).</font><br><font size=2 face="sans-serif"> Rajan: Check with David
Keaton to see if we are going to discuss the WANT macro issue on the agenda.
- Done. It is.</font><br><font size=2 face="sans-serif"> Fred: Send links to papers
of interest to CFP from N2319-N2323. - 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: Put a list of new
items that need to be done like the binding table and the totalorder* carry
over action items as well as adding in the min/max and augmented arithmetic
to a new part 4 revision.</font><br><font size=2 face="sans-serif"> Jim: Look at the part
3 X.2.6 change where the removal of the float _Imaginary, etc. part of
the list may imply those are not valid types anymore.</font><br><font size=2 face="sans-serif"> Jim: Get a document number
to submit the Part 3 as an Annex proposal to WG14 for the mailing.</font><br><font size=2 face="sans-serif"> Jim: Correct typo in page
1 of the proposal for part 4a ("As shown in the table below, C already
supports 22 *of* the 39...")</font><br><font size=2 face="sans-serif"> David H: Take a closer
look at the new proposal for part 4a (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_TS_18661-4a-2-20190213.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_TS_18661-4a-2-20190213.pdf</font></a><font size=2 face="sans-serif">)
to ensure it is good for submission via the reflector so it can be submitted
by Jim to WG14.</font><br><font size=2 face="sans-serif"> All: Review </font><a href=http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf</font></a><font size=2 face="sans-serif">within a week. If no changes, Jim will get a document number and send this
into WG14.</font><br><font size=2 face="sans-serif"> Jim: Look to see if there
is a place to put a note to address the alternate exception handling in
annex F to clarify how C specifies using default exception handling only.</font><br><font size=2 face="sans-serif"> Jim: Get a document number
to submit the Part 2 (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp2x-C2X-20190215.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp2x-C2X-20190215.pdf</font></a><font size=2 face="sans-serif">)
to WG14 for the mailing.</font><br><font size=2 face="sans-serif"> Fred: Create papers for
the SNAN initialization and unary + operation as CFP papers (CFP 1249,
1253, 1247, 1250) for future submission to WG14.</font><br><font size=2 face="sans-serif"> All: Consider why we didn't
have wide string from functions and if we should do them.</font><br><br><font size=2 face="sans-serif"><b> Next Meeting(s):</b></font><br><font size=2 face="sans-serif"> Monday, March 18th, 2019,
11:00 EST, 8:00 PST, 4PM UTC</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"> 754 revision:</font><br><font size=2 face="sans-serif"> Sponsor ballot
deadline at midnight today. Need to address 68 comments (most accepted).
Another draft (recirculation) will be issued. An asynchronous public review
which ends in a month with a current comment count of 5. Not looking at
major changes right now. Got enough Yes votes already.</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"> None.</font><br><br><font size=2 face="sans-serif"> C2X integration:</font><br><font size=2 face="sans-serif"> WG14 meeting (April
29th-May 3rd) pre-meeting mailing deadline: March 18th, 2019.</font><br><font size=2 face="sans-serif"> Meeting
information: </font><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2318.htm"><font size=2 color=blue face="sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2318.htm</font></a><font size=2 face="sans-serif">,
Venue information N2308 (linked to in the agenda).</font><br><br><font size=2 face="sans-serif"> Part 1:</font><br><font size=2 face="sans-serif"> Integrated
into a working C2X draft. Posted on the wiki.</font><br><br><font size=2 face="sans-serif"> Part 2:</font><br><font size=2 face="sans-serif"> A draft
is posted on the wiki for review.</font><br><font size=2 face="sans-serif"> Mike: The
preferred quantum exponents table was really nice.</font><br><br><font size=2 face="sans-serif"> Part 3:</font><br><font size=2 face="sans-serif"> A draft
as an annex is ready for review today.</font><br><br><font size=2 face="sans-serif"> Part 4ab:</font><br><font size=2 face="sans-serif"> 4a has an
updated proposal.</font><br><font size=2 face="sans-serif"> For 4b,
we should leave as a TS and add in the augmented arithmetic.</font><br><br><font size=2 face="sans-serif"> Part 5abcd:</font><br><font size=2 face="sans-serif"> Leave to
after the Spring 2019 WG14 meeting.</font><br><br><font size=2 face="sans-serif"> Action item details:</font><br><font size=2 face="sans-serif"> Jim: Post the draft of
Part 1 integrated into C2x on the CFP site.</font><br><font size=2 face="sans-serif"> (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/all-diffC2x-20190211.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/all-diffC2x-20190211.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/all-20190211.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/all-20190211.pdf</font></a><font size=2 face="sans-serif">)</font><br><font size=2 face="sans-serif"> No comments</font><br><br><font size=2 face="sans-serif"> Regarding Part 3 as annex
(</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20190205.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-20190205.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Jim: Make the first
change as per CFP1238.</font><br><font size=2 face="sans-serif"> Jim: Rework Part
3 as an Annex to add a note saying there is no _Decimal32x since IEC60559
doesn't have _Decimal32 as a basic type.</font><br><font size=2 face="sans-serif"> Jim: Make the _EPSILON
change as per CFP1238.</font><br><font size=2 face="sans-serif"> Jim: Make the fourth
change as per CFP1238 to add in the hyperbolic versions of cos/sin/tan.</font><br><font size=2 face="sans-serif"> Jim: Make the fifth
change as per CFP1238 for the list changes.</font><br><font size=2 face="sans-serif"> All: Take a look
at part 3 annex (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp3x-annex-</font></a><font size=2 face="sans-serif">20190119.pdf)
draft before next meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Jim: Some references
may need to be updated due to the moving nature of the C standard.</font><br><font size=2 face="sans-serif"> Looks good to submit
to WG14.</font><br><br><font size=2 face="sans-serif"> Jim: Update the proposal
to try again to integrate part 4a into C2X.</font><br><font size=2 face="sans-serif"> </font><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_TS_18661-4a-2-20190213.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_TS_18661-4a-2-20190213.pdf</font></a><br><font size=2 face="sans-serif"> Rajan: Typo on
first page (or the -> of the).</font><br><br><font size=2 face="sans-serif"> David: Check with IEEE
group to see if there is any implementations for Part 4b functions (hardware
or software).</font><br><font size=2 face="sans-serif"> David: Don't see
any C or Fortran implementations.</font><br><font size=2 face="sans-serif"> Keep as a TS.</font><br><br><font size=2 face="sans-serif"> All: Review the rationale
for part 5 a, b, c proposal.</font><br><font size=2 face="sans-serif"> Wait until after
current WG14 meeting.</font><br><br><font size=2 face="sans-serif"> All: Review </font><a href=http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdf</font></a><font size=2 face="sans-serif">.</font><br><font size=2 face="sans-serif"> Look to close this
one off via email.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Rajan: Say to WG14 that
CFP supports removing the WANT macros and leaving the rest as is due to
Fred's reasoning above.</font><br><font size=2 face="sans-serif"> See Rajan and Fred’s
email CFP 1242, 1243, 1244. Also Jim’s CFP 1261.</font><br><font size=2 face="sans-serif"> See WG14 email
15982 – 15993, 15995.</font><br><font size=2 face="sans-serif"> Related:</font><br><font size=2 face="sans-serif"> Jens idea
to rename many of the math functions</font><br><font size=2 face="sans-serif"> Jens idea
to “add a version macro (__STDC_MATH_VERSION__ ...) for the clauses where
we add interfaces that are not reserved, yet”</font><br><br><font size=2 face="sans-serif"> Jim: Versioning
is not really a floating point issue, it is more of a C standard issue.</font><br><font size=2 face="sans-serif"> Jens seemed
to want the WANT macros for the Annex F interfaces. We are OK with keeping
it.</font><br><font size=2 face="sans-serif"> Not in favor of
any name changes.</font><br><br><font size=2 face="sans-serif"> Fred: Send links to papers
of interest to CFP from N2319-N2323. See Fred’s email CFP 1246.</font><br><font size=2 face="sans-serif"> Discuss when Fred
is present.</font><br><br><font size=2 face="sans-serif"> David: min/max review/comparison
to IEEE:</font><br><font size=2 face="sans-serif"> Did not see anything
that was inconsistent.</font><br><br><font size=2 face="sans-serif"> David: augmented arithmetic
review/comparison to IEEE:</font><br><font size=2 face="sans-serif"> Seemed specified
for the default exception handling. Do we want to make the distinction
about overflow/underflow and inexact with the exception handling in the
C document?</font><br><font size=2 face="sans-serif"> Jim: C doesn't
have alternate exception handling so I don't think so.</font><br><font size=2 face="sans-serif"> *Jim: Look to see
if there is a place to put a note to address the alternate exception handling
in annex F.</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"> Draft for C2X integration
posted to wiki for review (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/cfp2x-C2X-20190215.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp2x-C2X-20190215.pdf</font></a><font size=2 face="sans-serif">)</font><br><font size=2 face="sans-serif"> Mike: Looks good!
Especially the preferred quantum exponents table.</font><br><font size=2 face="sans-serif"> Jim: Note that
removing the WANT macros will remove the header lists in the specs as well.</font><br><br><font size=2 face="sans-serif"> Unary operators. See Fred’s
email CFP 1249 and 1253.</font><br><font size=2 face="sans-serif"> Changes look to
be good.</font><br><br><font size=2 face="sans-serif"> Initialization with signaling
NaN macros. See Fred and Jim’s email CFP 1247, 1250.</font><br><font size=2 face="sans-serif"> Changes look to
be good.</font><br><br><font size=2 face="sans-serif"> Edge cases for fegetexceptflag.
See Fred and Jim’s email CFP 1256, 1260.</font><br><font size=2 face="sans-serif"> Seems good as it
is already. No need to change.</font><br><br><font size=2 face="sans-serif"> Why no wide character
string-from functions?</font><br><font size=2 face="sans-serif"> Consider why we
didn't have these already and if we should do them.</font><br><font size=2 face="sans-serif"> Ian: Probably
because you could always convert to regular strings then convert the regular
string to the wide character string.</font><br><br><font size=2 face="sans-serif"> Why no tgmath macros for
functions with pointer parameters? Question from Jens.</font><br><font size=2 face="sans-serif"> Jim: modf was the
one exclusion originally due to the pointer.</font><br><font size=2 face="sans-serif"> Rajan: The reason
was the specification for tgmath rules was based on float, double, long
double and so we just extended it to handle the new types we added. The
specification is complicated enough as is and adding in pointer specification
would make it much more complicated.</font><br><font size=2 face="sans-serif"> Rajan: The meta
question is do we need to do this? If people want to add pointer argument
based functions to the tg list then we can pursue this.</font><br><font size=2 face="sans-serif"> Leave it as is
for now.</font><br><br><font size=2 face="sans-serif">Regards,<br><br>Rajan Bhakta<br>z/OS XL C/C++ Compiler Technical Architect<br>ISO C Standards Representative for Canada<br>C Compiler Development<br>Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</font><br><BR>