<font size=2 face="sans-serif">2019/01/24: 10:00 CST:</font><br><font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim,
David H., Ian</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"> 2019/03/18: Libraries
no longer have the standards due to cost. The books on C++ didn't mention
this either.</font><br><font size=2 face="sans-serif"> Working copies
are in the Github repository linked to at </font><a href="https://isocpp.org/std/the-standard"><font size=2 color=blue face="sans-serif">https://isocpp.org/std/the-standard</font></a><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.
- Close (added to a list later on).</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. - Close since the TS is integrated into C2X and once the reference
to the IEEE standard gets updated this is a non-issue.</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"> Rajan: Say to WG14 that
CFP supports removing the WANT macros and leaving the rest as is due to
Fred's reasoning. - Carry over</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: 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. - Done.</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. - Done.</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. - Done.</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...") - Done.</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. - Done.</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. - Done.</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.
- Done.</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. - Done.</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. - Carry over.</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. - 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/Rajan: Create a slide
deck to show the changes made to make Part 3 into an Annex as WG14 requested.</font><br><font size=2 face="sans-serif"> Jim: Make CFP 1277 into
a C2X proposal.</font><br><font size=2 face="sans-serif"> Jim: Propose a footnote
to describe why there are no wide string strfrom functions (compose strfrom
with wide string conversion functions is sufficient) </font><br><br><font size=2 face="sans-serif"><b> Next Meeting(s):</b></font><br><font size=2 face="sans-serif"> Tuesday, April 23rd, 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"> Handled all the
open issues for recirculation. Preparing that draft which should occur
after March 22nd (for 10 days).</font><br><font size=2 face="sans-serif"> As mentioned before,
can only add new comments on new text, not old text.</font><br><font size=2 face="sans-serif"> Uncertainty factor:
IEEE boilerplate is full of bugs.</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"> 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"> CFP agenda items
P1 integration P2 integration</font><br><font size=2 face="sans-serif"> P3 as annex
– N2342</font><br><font size=2 face="sans-serif"> P4a proposal
- N2355</font><br><font size=2 face="sans-serif"> Update for
C2X payload functions – N2356</font><br><font size=2 face="sans-serif"> P4 CR for
rootn case differs from IEEE 754 – N2309</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Unclosed CR/DRs</font><br><font size=2 face="sans-serif"> P3 DR 13
- Type-generic macros for functions that round result to narrower type
</font><br><font size=2 face="sans-serif"> P1 DR 16r
- tgmath cbrt macro</font><br><font size=2 face="sans-serif"> P1 DR 20
- P1 CR for obsolescing DECIMAL_DIG</font><br><font size=2 face="sans-serif"> P1 DR 21
- printf of one-digit character string</font><br><font size=2 face="sans-serif"> P3 DR 22
- P3 CR for obsolescing DECIMAL_DIG</font><br><font size=2 face="sans-serif"> P2 CR 23
- llquantexp invalid case</font><br><font size=2 face="sans-serif"> P1 CR 24
- remainder NaN case</font><br><font size=2 face="sans-serif"> P1 CR 25
– totalorder parameters</font><br><font size=2 face="sans-serif"> DR 500 -
Ambiguous specification for FLT_EVAL_METHOD – marked as C2x</font><br><font size=2 face="sans-serif"> DR 501 -
Can DECIMAL_DIG be larger than necessary?</font><br><br><font size=2 face="sans-serif"> C2X integration:</font><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. See WG14 message 16214.</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><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><font size=2 face="sans-serif"> Jim: (a)
is related to evaluation methods.</font><br><font size=2 face="sans-serif"> Ian:
Similar to my action item.</font><br><font size=2 face="sans-serif"> Jim: I think
they are worth making another pitch on these.</font><br><font size=2 face="sans-serif"> Looking
to rework the proposals.</font><br><br><font size=2 face="sans-serif"> Action item details:</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><a href="http://wiki.edg.com/pub/CFP/WebHome/For_IEEE_754-2019-20190305.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/For_IEEE_754-2019-20190305.pdf</font></a><br><font size=2 face="sans-serif"> Jim: min/max: Since
parts 1 and 2 will soon be in C2X, the separate proposals (requested by
WG14) here may need to be combined again.</font><br><font size=2 face="sans-serif"> </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. See CFP 1268</font><br><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><a href=http://wiki.edg.com/pub/CFP/WebHome/n2342.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2342.pdf</font></a><br><font size=2 face="sans-serif"> *AI*: Jim/Rajan:
Create a slide deck to show the changes made to make Part 3 into an Annex
as WG14 requested.</font><br><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"> N2355.</font><br><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"> See David H’s
CFP 1272. </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2355.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2355.pdf</font></a><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.pdfwithin><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/update_for_C2X_payload_functions.pdfwithin</font></a><font size=2 face="sans-serif">a week. If no changes, Jim will get a document number and send this into
WG14. </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2356.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2356.pdf</font></a><br><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"> See CFP 1270, 1277.</font><br><font size=2 face="sans-serif"> directed rounding
-> rounding direction</font><br><font size=2 face="sans-serif"> *AI*: Jim: Make
CFP 1277 into a C2X proposal.</font><br><font size=2 face="sans-serif"> </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-"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp2x-</font></a><font size=2 face="sans-serif">C2X-20190215.pdf) to WG14 for the mailing. </font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2341.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2341.pdf</font></a><br><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"> Leave for next
meeting.</font><br><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. Note: Also mention CFP's appreciation to Jens for the
integration editing (done really well).</font><br><font size=2 face="sans-serif"> See Rajan, Fred,
and Jim’s email CFP 1242, 1243, 1244, 1261.</font><br><font size=2 face="sans-serif"> See WG14 email
15982 – 15983, 15985.</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"> Leave for next
meeting.</font><br><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><font size=2 face="sans-serif"> Sufficient to do
strfrom, convert to wide string.</font><br><font size=2 face="sans-serif"> *AI*: Jim: Propose
a footnote to describe why there are no wide string strfrom functions (compose
strfrom with wide string conversion functions is sufficient)</font><br><br><font size=2 face="sans-serif"><b> Other issues</b></font><br><font size=2 face="sans-serif"> Fred’s WG 14 papers</font><br><font size=2 face="sans-serif"> See Fred’s email
CFP 1246.</font><br><font size=2 face="sans-serif"> Decide on
our (CFP) position next meeting and Rajan to present our view.</font><br><font size=2 face="sans-serif"> </font><BR>