<div dir="ltr"><div>2025/03/12: 8:00 AM PDT</div><div class="gmail_quote gmail_quote_container"><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, Tue Ly, Maryam Karampour, Joshua Cranmer, David Hough, Fred Tydeman</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b>Agenda plus new items</b></p><p class="MsoNormal"> <a href="https://wiki.edg.com/pub/CFP/WebHome/n3516.pdf">https://wiki.edg.com/pub/CFP/WebHome/n3516.pdf</a> – These minutes should be read alongside the agenda, 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://wiki.edg.com/pub/CFP/WebHome/n3515.pdf">https://wiki.edg.com/pub/CFP/WebHome/n3515.pdf</a></p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Study group logistics</b></p><p class="MsoNormal"> Next meeting: 16 April 2025, 8:00 AM PDT</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: Has the server attackers at bay, for now.</p></div><div><p class="MsoNormal"><br></p><p class="MsoNormal"></p><p class="MsoNormal"><b>C documents</b></p><p class="MsoNormal"> There is a new C2Y draft 3467 Feb 2025. <a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3467.pdf">https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3467.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"> Jim: Please note the new draft, a fairly quick update from the previous version.</p><p class="MsoNormal"> </p><p class="MsoNormal"><b>IEEE 754 liaison</b></p><p class="MsoNormal"> David & Damian & Jerome: Much discussion but change is slow. A major topic is the fate of the 16-bit floating type.</p><p class="MsoNormal"> </p><p class="MsoNormal"><b>C++ liaison</b></p><p class="MsoNormal"> Joshua: Meeting of the numeric subgroup in recent meeting. The move to deprecate the fp environment still on the table.</p><p class="MsoNormal"> </p><p class="MsoNormal"><b>WG14</b></p><p class="MsoNormal"> Rajan:All papers but one were accepted. The paper on frexp and type double double has uncceptable language. WG14 had several ideas but no specific suggestion.</p><p class="MsoNormal"> Quoting Rajan from chat: These are models outside the C model. Should be in the library introduction section (7.1.4), "For the functions in math.h, if the implementation does not follow the model in 5.2.5.3.3, the results for the functions will be unspecified."</p><p class="MsoNormal"> Jim: Takes new action to offer a proposed fix arrived at in discussion.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Rajan: SIGFPE -- went with Action 4 in Fred's paper, n3378c:<br> <a href="https://wiki.edg.com/pub/CFP/WebHome/n3378c.htm">https://wiki.edg.com/pub/CFP/WebHome/n3378c.htm</a>.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Rajan: CFP got a round of applause from WG14. (Story told twice by popular demand.)</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Rajan: New draft of N3390 coming from Alex Celeste. The issue is whether the imaginary "I" is a constant or macro.<br> <a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3390.htm">https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3390.htm</a></p><p class="MsoNormal"><br></p><p class="MsoNormal"> Jim & Rajan: WG14 is developing a new process for simple wording changes to papers pending approval. This should expedite workflow.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Jim: Is it possible to support the imaginary types as a "pure extension", that is, not invalidating the implementation</p><p class="MsoNormal"> Rajan: Yes</p><p class="MsoNormal"> Jim: Can the current definitions be preserved? What about the imaginary suffix?</p><p class="MsoNormal"> Rajan: The imaginary suffix is part of the standard, so the new interpretation would be a change to the standard. </p><p class="MsoNormal"> Jim & Damian: The crux of of the matter is how to express "1.0i" as a pure imaginary unit when the standard defines it as a complex value with a possibly troublesome signed real part.</p>
<p class="MsoNormal"> </p><p class="MsoNormal"><b>TS-4 and TS-5 revisions</b></p><p class="MsoNormal"> Jim: Links in the agenda lead to drafts with a banner showing that final updates are due to be published "soon".</p><p class="MsoNormal"><br></p></div><div><p class="MsoNormal"><b>C23 integration</b></p><p class="MsoNormal"> None.</p><p class="MsoNormal"><br></p><p class="MsoNormal"><u></u></p><p class="MsoNormal"><b>Carry-over action items from last meeting </b></p><p class="MsoNormal"><b> </b>Damian: complex.h intro, cproj, and editorial suggestions.</p><p class="MsoNormal"> Damian: Might have a paper on the complex.h Intro up next week. cproj is done.</p><p class="MsoNormal"><br></p></div><div><p class="MsoNormal"><b>Action items from last meeting </b></p><p class="MsoNormal"> David: Draft statement on midpoint and interpolation.</p><p class="MsoNormal"> David: Done and forwarded by Rajan to WG14, where it was accepted.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Ly (spontaneous item): Will the complex library ever match the real library? E.g. cube root or sinepi?</p><p class="MsoNormal"> Jim: This will be considered for future discussion.</p><div><br></div> Jim: Review the comments on TS 5.</div><div> Done, with suggestions accepted by ISO, so they will appear.<br></div><div><br></div><div> Jerome: Rework the proposal for functions rounding to a narrow type. Finish by 19 Feb for Rajan to take to WG14 meeting.</div><div> Done and passed.</div><div><br></div><div> Jim: Write a paper proposing editorial changes for imaginary suffix, emphasizing editorial changes vs. technical changes.<br><p class="MsoNormal"> Done as WG14 paper n3500, due for next meeting.</p><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><b>Discussion of issues</b></p><p class="MsoNormal"> Action item from WG14</p><p class="MsoNormal"> Rajan: N3447 deals with evaluation of constants at compile time, outside the execution environment. </p><p class="MsoNormal"> Jim: Proposes better wording for the description, which Rajan takes an action for.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Midpoint and interpolation functions in C</p><p class="MsoNormal"> Rajan: WG14 is happy with David's reply.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> cproj cleanup</p><p class="MsoNormal"> Jim: All of the other complex functions are defined generally across the family. But cproj has a definition in terms of type double. An added sentence makes that difference clearer.</p><p class="MsoNormal"> Jiim: Offers several comments re. the form of the proposal, with options to prepare in Word, or Google Docs, or elsewhere.</p><p class="MsoNormal"> Fred: Process comment -- I do my proposals in raw html.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> complex.h introduction</p><p class="MsoNormal"> taken as an action item.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Errors in draft 3435</p><p class="MsoNormal"> Jim: Parenthetical about "infinitary" is not yet removed but Rajan says it's in the works.</p><div><br></div> Imaginary I macro and i suffix issues</div><div> Jim: Rajan has proposed fixes and the change is coming.<br><p class="MsoNormal"><br></p><p class="MsoNormal"></p></div><div><p class="MsoNormal"><b>Other issues:</b></p></div><div> WG 14 proposal process</div><div> Jim: Discussed earlier.</div><div><br></div> nexttoward exceptions</div><div dir="ltr"> Ly: The issue is raising exceptions for 0 or subnormal results. It's not clear that one or both of ERRNO and the fp exceptions must be indicated if the result is subnormal or zero. Whether it's raised is implementation-defined in the standard. Annex F does not have that latitude.</div><div dir="ltr"> Ly: In Linux, we don't want to spend the execution time to signal the exception.. Linux has the newer forms nextup and nextdown but they're not generally available in programming environments.<br><div><br></div><div><b>Adjournment</b></div><div><div><p class="MsoNormal"> 9:26 AM PDT</p><p class="MsoNormal">-----------------------------------------------</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Action items to be carried over:</b></p><p class="MsoNormal"> None.</p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>New action items:<u></u><u></u></b></p><p class="MsoNormal"> Jim: Draft a paper with suggestion for frexp and double double to address the WG14 objections.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Rajan: Send a note to WG14 about the N3447 issue.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Damian & Jim: Tune up the cproj proposal suitable for WG14.</p><p class="MsoNormal"><br></p><p class="MsoNormal"> Ly: Send email to CFP about the next____() issues.</p><p class="MsoNormal"><br></p></div></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div><b>Discussion issues to be carried over:</b></div><div><p class="MsoNormal"> None.<br></p><br></div><div>Respectfully submitted.</div><div><br></div><div dir="ltr">-Jerome Coonen<div> 650.996.4738</div><div> <a href="mailto:jcoonen@gmail.com" target="_blank">jcoonen@gmail.com</a></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>