<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> <b class="">Attendees</b>: Rajan, Fred, Jim, David H, Mike, Ian</span><br class=""><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> New agenda items:</b></span><br class=""><font face="sans-serif" size="2" class=""> Jens email (SC22WG14.17316)</font><font face="sans-serif" class=""><font size="2" class=""> WG14 gorvernance </font></font><br class=""><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> Carry over action items:</b></span><br class=""><font face="sans-serif" size="2" class=""> CFP: Put the tgmath redefinition as a proposal to</font><font face="sans-serif" class=""><font size="2" class=""> the standard once we have a base document with TS Part 3 in it. Carry over </font></font><font face="sans-serif" size="2" class="">again.</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" class=""><font size="2" class=""> </font></font><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> Last meeting action items:</b></span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span><font face="sans-serif" size="2" class=""> CFP: Follow up on CFP1419 via email. DONE<br class=""> Jim: Create a WG14 paper for the next Spring 2020 WG14 meeting along the lines of CFP1411. DONE</font><div class=""><font face="sans-serif" size="2" class=""><br class=""></font><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> New action items:</b></span><br class=""><font face="sans-serif" size="2" class=""> Fred: Update erange proposal based on CFP 1437 and CFP teleconference discussion.</font><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Jim: Submit </span><font face="sans-serif" size="2" class=""><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf" class="">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf</a> to WG14</font><span style="font-family: sans-serif; font-size: 10pt;" class="">.</span></div><div class=""><span style="font-family: sans-serif; font-size: 10pt;" class=""> </span><span style="font-family: sans-serif; font-size: small;" class="">Rajan: Compile example code in </span><font face="sans-serif" size="2" class=""><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf" class="">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</a></font><span style="font-family: sans-serif; font-size: small;" class="">.</span></div><div class=""><span style="font-family: sans-serif; font-size: small;" class=""> Jim: Choose how to attach footnote in </span><font face="sans-serif" size="2" class=""><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf" class="">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</a>; mention the other approach in the problem description.</font></div><div class=""><font face="sans-serif" size="2" class=""> 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.</font></div><div class=""><font face="sans-serif" size="2" class=""> David H: Draft words to recommend honoring properties of math functions that would follow automatically from correct rounding.</font></div><div class=""><font face="sans-serif" size="2" class=""> Jim: Find a place for words about math function properties. Coordinate with David H (previous AI).</font></div><div class=""><span style="font-family: sans-serif; font-size: small;" class=""> Jim: Draft a proposal to change the return words for powr and add the footnote (presented in the meeting) to justify powr.</span></div><div class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> Next Meeting(s):</b></span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Thursday, January 9th, 2020, 11:00 EST, 8:00 PST, 4PM UTC</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Same teleconference number.</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Please notify the group if this time slot does not work.</span><br class=""><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> Discussion:</b></span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> 754 revision:</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span><font face="sans-serif" size="2" class="">This is the final resting place for the public records of 754-2019 development, <br class=""><a href="http://grouper.ieee.org/groups/msc/ANSI_IEEE-Std-754-2019" class="">http://grouper.ieee.org/groups/msc/ANSI_IEEE-Std-754-2019</a></font></div><div class=""><font face="sans-serif" size="2" class="">in the IEEE SA MSC page.<br class=""><a href="http://grouper.ieee.org/groups/msc/index.html" class="">http://grouper.ieee.org/groups/msc/index.html</a></font></div><div class=""><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> C++ Liaison:</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Nothing.</span></div><div class=""><font face="sans-serif" size="2" class=""><br class=""></font></div><div class=""><font face="sans-serif" size="2" class=""> Jens’s email (SC22WG14.17316) WG14 governance</font></div><div class=""><font face="sans-serif" size="2" class=""> Discussed content and relevance to CFP.</font></div><div class=""><font face="sans-serif" size="2" class=""> Concerns about transition to new editor and work in progress.</font></div><div class=""><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> WG14 meeting in Ithaca</span></div><div class=""><font face="sans-serif" size="2" class=""> See CFP 1432 - Rajan’s report on CFP related issues</font></div><div class=""><font face="sans-serif" size="2" class=""> Excerpts …</font></div><blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;" class=""><div class=""><font face="sans-serif" size="2" class="">Here is a summary of the results for what was discussed for floating point papers yesterday. Note that we have one action item (reword N2400), and also the proposal for Part 5 a and b went a lot better than last time and we got on the verge of approval (but not quite).</font></div><div class=""><font face="sans-serif" size="2" class=""> N2384 Thomas, C2X proposal - F.8 update</font></div><div class=""><font face="sans-serif" size="2" class=""> Goes into C2X.</font></div><div class=""><font face="sans-serif" size="2" class=""> N2400 Thomas, C2X proposal - why no wide string strfrom functions</font></div><div class=""><font face="sans-serif" size="2" class=""> CFP to send this text to the editor as a footnote and a recipe (steps to get wide string version of strfrom code example) form.</font></div><div class=""><font face="sans-serif" size="2" class=""> N2406 Tydeman, SNAN: initialization and unary +</font></div><div class=""><font face="sans-serif" size="2" class=""> Goes into C2X.</font></div><div class=""><font face="sans-serif" size="2" class=""> N2407 Thomas, Proposal for C2X - TS 18661-5abc supplementary attributes</font></div><div class=""><font face="sans-serif" size="2" class=""> Straw poll: Does the committee want TS 18661-5a to be brought into C2X?</font></div><div class=""><font face="sans-serif" size="2" class=""> Result: 5/3/5. Not quite approval.</font></div><div class=""><font face="sans-serif" size="2" class=""> Straw poll: Does the committee want TS 18661-5b to be brought into C2X?</font></div><div class=""><font face="sans-serif" size="2" class=""> Result: 4/3/6. Not approved. </font></div><div class=""><font face="sans-serif" size="2" class=""> N2416 Thomas, Proposal for C2X - floating-point negation and conversion</font></div><div class=""><font face="sans-serif" size="2" class=""> Goes into C2X.</font></div><div class=""><font face="sans-serif" size="2" class=""> N2424 Thomas, Proposal for C2X proposal – Why logp1?</font></div><div class=""><font face="sans-serif" size="2" class=""> Goes into C2X. </font></div></blockquote><div class=""><font face="sans-serif" size="2" class=""> The naming proposal did not pass and there were no action items for CFP from it. </font><span style="font-family: sans-serif; font-size: small;" class="">WG14 didn’t get into the cr prefix or NaN and infinity macro names.</span></div><div class=""><font face="sans-serif" size="2" class=""> N2409 (reserved names) is something we should track for changes affecting CFP.</font></div><div class=""><font face="sans-serif" size="2" class=""> There was no resolution about intmax_t.</font><span style="font-family: sans-serif; font-size: small;" class=""> </span></div><div class=""><font face="sans-serif" size="2" class=""> </font></div><div class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> C2X integration (</span><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf" class=""><span style="font-size: 10pt; color: blue; font-family: sans-serif;" class="">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf</span></a><span style="font-size: 10pt; font-family: sans-serif;" class="">):</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Draft includes TS 1, 2, and 4a</span></div><div class=""><font face="sans-serif" size="2" class=""> TS 5abc inclusion into C2X nearly passed. Might should be resubmitted later.<br class=""> Part 3 integration status in question, given Jen’s email.</font></div><div class=""><font face="sans-serif" size="2" class=""> Too early to update parts not integrated into C2X. Need ISO approval to republish TS.<br class=""></font><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""><b class=""> Action item details:</b></span></div><div class=""><font face="sans-serif" size="2" class=""> CFP: Follow up on CFP1419 via email.<br class=""> See CFP 1437.</font></div><div class=""><font face="sans-serif" size="2" class=""> Talked through changes proposed in 1437. </font></div><div class=""><font face="sans-serif" size="2" class=""> Agreed to be consistent on saying “magnitude of”, even if redundant as in “magnitude of positive finite x is too large. </font></div><div class=""><font face="sans-serif" size="2" class=""> Agreed to split non-symmetric cases to state positive and negative cases separately, as in 1437, e.g., in exp and expm1. </font></div><div class=""><font face="sans-serif" size="2" class=""> Agreed to “A range error occurs for some finite x, depending on p” for ldexp, and similar words for scalbn and scalbln and elsewhere where characterization of range errors is complicated. </font></div><div class=""><font face="sans-serif" size="2" class=""> Agreed to “A range error occurs for some finite arguments” for fdim. </font></div><div class=""><font face="sans-serif" size="2" class=""> Agree to avoid “may occur” in general.</font></div><div class=""><font face="sans-serif" size="2" class=""> *AI*: Fred: Update erange proposal based on CFP 1437 and CFP teleconference discussion.</font><br class=""></div><div class=""><font face="sans-serif" size="2" class=""><b class=""><br class=""></b> Jim: Create a WG14 paper for the next Spring 2020 WG14 meeting along the lines of CFP1411.<br class=""> </font><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf" class="">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf</a></div><div class=""><font face="sans-serif" size="2" class=""> Reviewed.</font></div><div class=""><font face="sans-serif" size="2" class=""> Ok to submit to WG14? Yes.<br class=""></font><span style="font-size: small; font-family: sans-serif;" class=""> </span><span style="font-family: sans-serif; font-size: small;" class="">*AI*:</span><span style="font-size: small; font-family: sans-serif;" class=""> jJim submit to WG14.</span></div><div class=""><span style="font-family: sans-serif; font-size: small;" class=""><br class=""></span></div><div class=""><span style="font-family: sans-serif;" class=""><font size="2" class=""> </font></span><span style="font-family: sans-serif; font-size: small;" class="">From WG14:</span></div><div class=""><font face="sans-serif" size="2" class=""> N2400 Thomas, C2X proposal - why no wide string strfrom functions<br class=""> CFP to send this text to the editor as a footnote and a recipe (steps to get wide string version of strfrom code example) form. <br class=""> See CFP 1436.</font></div><div class=""><font face="sans-serif" size="2" class=""> </font><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf" class="">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</a></div><div class=""><font face="sans-serif" size="2" class=""> </font><span style="font-family: sans-serif; font-size: small;" class="">*AI*: Rajan: compile code in example.</span></div><div class=""><font face="sans-serif" size="2" class=""> </font><span style="font-family: sans-serif; font-size: small;" class="">*AI*: Jim: </span><span style="font-family: sans-serif; font-size: small;" class="">Choose how to attach footnote and </span><font face="sans-serif" size="2" class="">mention the other approach in the problem description.</font></div><div class=""><br class=""></div><div class=""><b style="font-family: sans-serif; font-size: 10pt;" class=""> Other issues:</b></div><div class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span><font face="sans-serif" size="2" class="">N2426 -- naming issues<br class=""> Shall we propose changing to cr_? Agreed.</font></div><div class=""><font face="sans-serif" size="2" class=""> Rajan: Include with other changes in response to naming paper.<br class=""> AI: Jim draft a proposal and include other suggested changes in response to naming paper.</font></div><div class=""><font face="sans-serif" size="2" class=""><br class=""></font></div><div class=""><font face="sans-serif" size="2" class=""> Specifying more special cases for math functions, e.g., periodicity for half-revolution trig functions. Perhaps as recommended practice.<br class=""> Are we going to propose adding anything?<br class=""> Jim: Could there be a note or recommended practice for implementations to honor function properties that would hold if the function were correctly rounded, e.g., monotonicity, periodicity, exact cases, ertc.<br class=""></font><div class=""><font face="sans-serif" size="2" class=""> *AI*: David H: Draft words to recommend honoring properties of math functions that would follow automatically with correct rounding.</font></div><div class=""><font face="sans-serif" size="2" class=""> *AI*: Jim: Find a place for words about math function properties. Coordinate with David H.</font></div></div><div class=""><font face="sans-serif" size="2" class=""><br class=""></font></div><font face="sans-serif" size="2" class=""> powr</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> Currently says “The powr functions compute x raised to the power y as e ^ (y log x). …” and “The powr functions return x^y.” </font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> Would it be better to say “The powr functions return e ^ (y log x).”? Agreed yes.<br class=""> Jens suggested a note about pow vs powr. </font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> Jim: How about a footnote attached to the first sentence in the Description where the footnote is:<br class=""> (*) Restricting the domain to that of the formula e ^ (y * log(x)) is intended to better meet expectations for a continuous power function and to allow more efficient implementation by avoiding some case analysis.</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> </font><span style="font-family: sans-serif; font-size: small;" class="">*AI*: Jim: draft a proposal to change the return words and add a footnote.</span><font face="sans-serif" size="2" class=""><br class=""><br class=""> Attributes - recent WG14 email thread<br class=""> Does this pertain to CFP?</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> Jim: A vehicle for CFP pragma functionality?</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> Rajan: current ideas are for attributes that don’t apply to blocks, so no.</font></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="sans-serif" size="2" class=""> </font><font face="sans-serif" size="2" class=""> </font><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span></div><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Followup on what does “normalized” mean in C? See CFP 1399</span><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> Defer.</span></div><div class=""><font face="sans-serif" size="2" class=""><br class=""></font></div><div class=""><font face="sans-serif" size="2" class="">- Jim Thomas<br class=""></font><br class=""><span style="font-size: 10pt; font-family: sans-serif;" class=""> </span></div></div></body></html>