<div dir="ltr"><div>2026/02/18: 8:00 AM PDT/3:00 PM UTC</div><div class="gmail_quote gmail_quote_container"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div>[Please submit proposed changes to these minutes to Jerome or to the group. Revision changes appear at the bottom.]</div><div><br></div><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><p class="MsoNormal"><b>Attendees</b></p><p class="MsoNormal"> Jim Thomas, Rajan Bhakta, Jerome Coonen, Damian McGuckin, Joshua Cranmer, Fred Tydeman, David Hough, Ariel Burton</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b>Updated agenda plus new items</b></p><p class="MsoNormal"> <a href="https://cfp-wiki.esi.com.au/pub/CFP/WebHome/CFP%20meeting%20agenda-20260318-update4.pdf?_t=1773865597" target="_blank">https://cfp-wiki.esi.com.au/pub/CFP/WebHome/CFP%20meeting%20agenda-20260318-update4.pdf?_t=1773865597</a> – These minutes should be read alongside the agenda, in this case a rare 4th update, with its many reference links.</p><p class="MsoNormal"><b><br></b></p><p class="MsoNormal"><b>Previous meeting notes</b></p><p class="MsoNormal"> <a href="https://mailman.oakapple.net/pipermail/cfp-interest/2026-February/003807.html" target="_blank">https://mailman.oakapple.net/pipermail/cfp-interest/2026-February/003807.html</a> 2026/02/18 Meeting notes</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Study group logistics</b></p><p class="MsoNormal"> Next meeting: 15 April 2026, 8:00 AM PDT/3:00 PM UTC</p><p class="MsoNormal"> ISO Zoom teleconference</p><p class="MsoNormal"> Please notify the group if this time slot does not work.</p><p class="MsoNormal"> David: Computer centers in Brazil rent time to bad players who attack system around the world, often for "protection" money. Penniless though it may be, our reflector has suffered collateral damage in the chaos. </p><p class="MsoNormal"> Damian: Be aware that when you upload an updated file (with the same name) to the wiki, the upload may be slow after the Nth copy, for N seven to nine. This is due in part to the automated backup mechanism.</p><p class="MsoNormal"><br></p></div><div><p class="MsoNormal"></p><p class="MsoNormal"><b>C documents</b></p><p class="MsoNormal"> The latest C2Y draft is N3783 Jan. 2026 <a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3783.pdf" target="_blank">https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3783.pdf</a></p><p class="MsoNormal"> C23 has been published ISO/IEC 9899, available for purchase. <a href="https://www.iso.org/standard/82075.html" target="_blank">https://www.iso.org/standard/82075.html</a></p><p class="MsoNormal"> </p><p class="MsoNormal"><b>IEEE 754 liaison</b></p><p class="MsoNormal"> Damian: Trying nail Round-To-Odd and language. There's a new probabilistic rounding proposal. Propagation of NaNs is a continuing issue. At David Keaton's suggestion, Damian is proposing to be liaison between 754 and WG14/CFP.</p><p class="MsoNormal"> </p><p class="MsoNormal"><b>C++ liaison</b></p><p class="MsoNormal"> Joshua: Next meeting is the week of 23 March. Four papers are of interest:</p><p class="MsoNormal"> 1) <a href="http://wg21.link/p3938" target="_blank">http://wg21.link/p3938</a> -- clarifies the wording, like "infinity" and "NaN", needed to talk about the values floating point types might take.</p><p class="MsoNormal"> 2) <a href="http://wg21.link/p3899" target="_blank">http://wg21.link/p3899</a> -- clarify the behavior on floating point overflow.</p><p class="MsoNormal"> 3) <a href="http://wg21.link/p3935" target="_blank">http://wg21.link/p3935</a> -- update <cmath.h> to align with C23 <math.h>.</p><p class="MsoNormal"> 4) <a href="http://wg21.link/p3864" target="_blank">http://wg21.link/p3864</a> -- Use the prefix "cr_" to add correctly-rounded math functions to the library. </p><p class="MsoNormal"><br></p><p class="MsoNormal"> Joshua & Group: These functions use "to nearest with ties to even" rounding regardless of any prevailing rounding direction modes.</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>WG14 update</b></p><p class="MsoNormal"> Rajan: Reviews detailed email summary (linked in the agenda). Most items pass with just 5 minutes of discussion apiece: preferred quantum exponent (N3703); clean up frexp, et al. (N3704); range bounds for math functions (with editorial changes) (N3731); floating expressions in translation time (N3732). </p><p class="MsoNormal"> Rajan: In our proposals until now, we use a red strikethrough typeface for deletion and green for insertion. WG14 requests that we also underline insertions. The issue is red-green color blindness.</p><p class="MsoNormal"> Group: Perhaps use blue for insertion. Will try blue underline in new proposals this month.</p><p class="MsoNormal"> Rajan: The contentious issue, which took most of the CFP time in the meeting, was the proposal to refine the language of error reporting (3731). The proposal italicizes "occurs" to make precise the notion that what we generally view as a mathematical exceptional case "occurs as an error" in the C environment in just specific circumstances. WG14 said that defining that usage of "occur(s)" might affect other usage of the word in the standard. The motion passed, with the removal of the italics for "occurs".</p><p class="MsoNormal"> Jerome: Takes action to revisit this proposal and this usage.</p><p class="MsoNormal"> </p><p class="MsoNormal"><b>TS-4 and TS-5 revisions</b></p><p class="MsoNormal"> Jim: Joseph Meyers has emailed about the error in TS-4 that CFP discovered. It acknowledges the issue and the proposed fix, though there is no planned action yet.</p></div><div><p class="MsoNormal"><br></p><p class="MsoNormal"><b>News</b></p><p class="MsoNormal"> None</p><p class="MsoNormal"><br></p><p class="MsoNormal"><u></u></p><p class="MsoNormal"><b>Carryover action items from last meeting </b></p></div><div> Group: Think about where CFP is headed.</div><div> Carry over<br><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Action items from last meeting </b></p></div><div> Damian: Investigate the current state of default rounding(s) in 60559 and whatever is being discussed in the committee about changes, especially in decimal.</div><div> Closed -- there is the option to have the default rounding break ties away from 0.</div><div><br></div> Damian: Arrange to take the email archive from David. Discuss the status going forward.</div><div> Carry over</div><div dir="ltr"><br></div><div dir="ltr"> Damian: Document the wiki backup protocol.<br> Done</div><div dir="ltr"><br></div><div dir="ltr"> Jim & Jerome: Draft proposal re. double_t semantics and send a note to Joseph about the proposed solution.<br> Done</div><div dir="ltr"><br></div><div dir="ltr"> Jerome & Damian: Write a proposal to repair fromfp and enhance Table F.2.</div><div> Carry over</div><div dir="ltr"><br> Jim & Damian: Look at the language around rounding direction in Damian's Annex F paper and make a proposal to CFP about how to go forward.<br><div> Done</div><div><br></div></div><div dir="ltr"><div><b>Discussion of issues</b></div><div><b> </b>Conflicting requirements for double_t</div><div> Rajan: Editorially, prefer to have underscore along with color for additions.</div><div> Group: Good to submit. Action.</div><div dir="ltr"><br></div></div><div dir="ltr"> Annex F special cases</div><div> Damian: Reviews many special cases, including some worked worked out with Fred. Will use square brackets for rationale items interleaved with proposal items.</div><div> Rajan & Group: In such a long proposal, burying the rationale at the end does not help the reader.</div><div> Jim: In frexp, "value" is the parameter, not "x".</div><div> Jim: modf is like frexp, not bound to a 60559 function, so could signal “inexact” or “underflow” unless specified to not signal any exceptions. The parameter "value" needs to be rationalized, too.</div><div> Damian: Amid the pages of editorial changes, there are just two technical changes: scalbn with a signaling NaN and the addition of a compoundn special case Fred noticed was missing.</div><div> Jim & Rajan: The changes are so small that we can just have one paper with both (2) technical changes and (many) editorial changes.</div><div> Jim: Suggests making the uniform syntax more explicit at the start of the proposal, giving the reader a better sense of the broad cleanup undertaken in the proposal. </div><div> Rajan: WG14 doesn't like long papers, but the items are small here so it may get through. </div><div> Jim: Encourages group to spend the time to review the next draft in detail. The challenge here is to get it all right -- and to convince WG14 that we have it all right.</div><div><br></div><div dir="ltr"> Rounding direction language</div><div> Jim: Reviews his paper with Damian presenting terms to be used going forward.</div><div> Damian: Already in use in Annex F documents.</div><div> Jim: There is no proposal to update the whole standard with this language.</div><div> Group: Locution "standard/binary and decimal types" is a bit misleading.<br> Rajan & Group: Good clarification</div><div dir="ltr"><br></div><div dir="ltr"><div><b>Other issues</b></div></div><div dir="ltr"><div> None</div><div><br></div></div><div dir="ltr"><div><b>Adjournment</b></div><div><p class="MsoNormal"> 10:03 AM PDT</p><p class="MsoNormal">-----------------------------------------------</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Action items to be carried over</b></p><div dir="ltr"> Group: Think about where CFP is headed.</div><div dir="ltr"><br></div><div dir="ltr"> Jerome & Damian: Write a proposal to repair fromfp and enhance Table F.2.</div><div dir="ltr"><br></div><p class="MsoNormal"><b>New action items</b></p><p class="MsoNormal"> Jim: Add agenda item to fix range bounds problem for complex fcns (as done for real functions in N3731).</p><p class="MsoNormal">'</p><p class="MsoNormal"> Jerome: Research usage of "occur(s)" and how it applies to proposal n3737.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Jim: Submit doble_t proposal.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Damian: In the Annex F special cases paper, add the function header to the code examples (which will clarify the usage of the parameters).</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Jim & Damian: Review the wording of F.10.4.7 and F.10.4.9 and propose any changes.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Damian: Update the Annex F Special Cases paper as technical plus editorial.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Damian & Jerome: Send a note to CFP about the usage of "current rounding direction".</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Damian: Draft a proposal for a new table (F.3) in Annex F mapping the rounding direction attributes from 60559 to the language of C2Y.</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Carryover discussion items</b></p><div dir="ltr"><div dir="ltr"> Fixes to symbols: minus signs and hyphens, etc.</div><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr"> Complex and signaling NaNs<br><br></div><div dir="ltr"> INFINITY and _Float16<br></div><div dir="ltr"><br></div><div dir="ltr"> Function result vs return value<br></div> CFP future<br><br></div><div dir="ltr"> Editorial issues F.2.2<br></div><div dir="ltr"><br></div><div dir="ltr"> Editorial issues F.3, etc.<br></div><div dir="ltr"><br></div><div dir="ltr"> Editorial issues F.10.1</div></div></div><div dir="ltr"><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div><div><b>Signoff</b></div></div><div> Respectfully submitted.</div><div><br></div><div dir="ltr">-Jerome Coonen<div><br></div></div></div></div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div>
</div></div>
</div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div>
</div></div>
</div></div>
</div></div>