<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Some corrections in <span style="color:red">red </span>below. My apologies for not correcting them before sending out the minutes (in too much of a rush to get to my action items)!<o:p></o:p></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<p class="MsoNormal" style="mso-line-height-alt:.75pt"><span lang="EN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-line-height-alt:.75pt"><span style="font-size:1.0pt;color:white">ZjQcmQRYFpfptBannerEnd<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <b>Attendees</b>: Rajan, Jim, Fred, Damian, Jerome, Joshua, David<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <b>New agenda items</b> (<a href="https://wiki.edg.com/pub/CFP/WebHome/CFP%20meeting%20agenda-20240313-update.pdf">https://wiki.edg.com/pub/CFP/WebHome/CFP%20meeting%20agenda-20240313-update.pdf</a>):<o:p></o:p></p>
<p class="MsoNormal"> None.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Previous meeting notes:</b><o:p></o:p></p>
<p class="MsoNormal"> See CFP2976 (<a href="http://mailman.oakapple.net/pipermail/cfp-interest/2024-January/002990.html">http://mailman.oakapple.net/pipermail/cfp-interest/2024-January/002990.html</a>).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Next Meeting(s):</b><o:p></o:p></p>
<p class="MsoNormal"> April 10, 2024, 4PM UTC<o:p></o:p></p>
<p class="MsoNormal"> ISO Zoom teleconference<o:p></o:p></p>
<p class="MsoNormal"> Please notify the group if this time slot does not work.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> New action items:</b><o:p></o:p></p>
<p class="MsoNormal"> Rajan: Send the WG14 editorial comments from CFP to CFP.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: For C2Y issue 5, reword H.3.6 and 5.2.5.3.2#28 to "If a signaling NaN macro (optionally preceded by the unary + or - operator) is used for initializing an object of the same type that has static or thread storage duration, the
object is initialized with a signaling NaN value."<o:p></o:p></p>
<p class="MsoNormal"> Jim: Fix the suggested changes section in CFP3020's paper to point to N3219 (instead of the incorrect N3619 as it currently is) and send it out to WG14.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Submit the paper resolving C2Y Issue 17 (CFP3022) to WG14.<o:p></o:p></p>
<p class="MsoNormal"> Jim/Jerome/Damian: Follow up on C26 issue 1.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP3003 to the issues list.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Draft up changes to incorporate CFP3006.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP3007 to the C26 issues list.<o:p></o:p></p>
<p class="MsoNormal"> Damian: Get a list of editorial issues in Annex G and send them out for future submission to WG14.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Action items to be carried over:</b><o:p></o:p></p>
<p class="MsoNormal"> None.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> C++ liaison:</b><o:p></o:p></p>
<p class="MsoNormal"> None.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> WG14 (added):</b><o:p></o:p></p>
<p class="MsoNormal"> See CFP3008 and follow ons.<o:p></o:p></p>
<p class="MsoNormal"> No editorial review group resolution meeting scheduled yet.<o:p></o:p></p>
<p class="MsoNormal"> Next WG14 meeting (virtual) is June 10-14th, 2024.<o:p></o:p></p>
<p class="MsoNormal"> ^Rajan: Send the WG14 editorial comments from CFP to CFP.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> C23 integration</b><o:p></o:p></p>
<p class="MsoNormal"> C23 drafts:<o:p></o:p></p>
<p class="MsoNormal"> C23 working draft n3219 - July 2, 2023 - For CFP review only. Do not distribute.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Carry over action items</b><o:p></o:p></p>
<p class="MsoNormal"> None<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Action items from previous meeting (Done unless stated otherwise)</b><o:p></o:p></p>
<p class="MsoNormal"> Fred: C26: Issue 5: Are there any <math.h> macros with the same issue? Should words be added to an introduction section in <float.h>?<o:p></o:p></p>
<p class="MsoNormal"> See [Cfp-interest 2999] <math.h> macros and exceptions (and follow on CFP 3031)<o:p></o:p></p>
<p class="MsoNormal"> OK with using CFP 3031 as the direction for the resolution to the issue.<o:p></o:p></p>
<p class="MsoNormal"> Jim: For SNAN macro recommended practice (in F.2.2#6 on), don't see the issue.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Will look at it.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: The H.3#6 should have the optional unary operator be after the initializing an object to not make that optional mandatory (in a specific way of reading it).<o:p></o:p></p>
<p class="MsoNormal"> Jim: I'm OK with that.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Doesn't adding the -/+ cause raising a signal?<o:p></o:p></p>
<p class="MsoNormal"> Jim: No, this is not an expression. 754 has a set of operations that do not signal.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:red"> Damian: Yes, that's true.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red"> Jim: Things like copysign.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red"> Damian: Other operations like Abs, Negate and Copy as well. (Post meeting reference: IEEE 753 5.5.1).<o:p></o:p></span></p>
<p class="MsoNormal"> ^Rajan: For C2Y issue 5, reword H.3.6 and 5.2.5.3.2#28 to "If a signaling NaN macro (optionally preceded by the unary + or - operator) is used for initializing an object of the same type that has static or thread storage duration,
the object is initialized with a signaling NaN value."<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Fred: C26: Issue 9: Look at original CFP messages to see if 3.10 (Correctly rounded definition) might cover it.<o:p></o:p></p>
<p class="MsoNormal"> See [Cfp-interest 3000] CFP issue #9<o:p></o:p></p>
<p class="MsoNormal"> Fred: Fine with it.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: It is in 3.12 in N3219.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: C26: Issue 4: Draft a paper as per the resolution in the issues list.<o:p></o:p></p>
<p class="MsoNormal"> See [Cfp-interest 3020 and follow ons] Re: printf and rounding recommendation<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Fix the suggested changes section in CFP3020's paper to point to N3219 (instead of the incorrect N3619 as it currently is) and send it out to WG14.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: C26: Issue 17: Draft a paper as per the resolution in the issues list.<o:p></o:p></p>
<p class="MsoNormal"> See [Cfp-interest 3022] C2Y Issue 17<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Submit the paper resolving C2Y Issue 17 (CFP3022) to WG14.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jerome: C26: Issue 1: Get definitions of terms relating to the issue for 754 and C and regular math.<o:p></o:p></p>
<p class="MsoNormal"> See [Cfp-interest 3016] Re: about C26 Issue 1<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Will need to remain an open issue until we get closure from the 754 people. We could make the changes I suggested in C, but better to wait for 754.<o:p></o:p></p>
<p class="MsoNormal"> Jim: The 754 term we need to be consistent with is the divide-by-zero exception. It doesn't classify the different types of errors. C needs the categories due to errno.<o:p></o:p></p>
<p class="MsoNormal"> Damian: I think singularity is exactly what you want.<o:p></o:p></p>
<p class="MsoNormal"> Fred: So log(0) is a singularity error?<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Yes, on 754 systems.<o:p></o:p></p>
<p class="MsoNormal"> Fred: If you make this change for log gamma, you need to do it for all other cases like log(0).<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Yes, I think you are right.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Wider issue, see CFP-2996.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Don't most mathematicians consider pow(0,0) to be 1?<o:p></o:p></p>
<p class="MsoNormal"> Damian: Yes.<o:p></o:p></p>
<p class="MsoNormal"> Jim: No. Because the limit does not exist.<o:p></o:p></p>
<p class="MsoNormal"> David: It's an exception since there is no right answer. The default is arbitrary. You should get an exception for pow(0,0). I had forgotten that.<o:p></o:p></p>
<p class="MsoNormal"> Joshua: All the pown, powr, and pow say they return 1 without exceptions in IEEE.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: I think some people wanted NaN since it is dangerous to say anything since 0, 1, or infinity are all valid.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Kahan said you had to have 1 as anything else would cause problems.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Now I'm thinking of leaving "mathematical function" as not fully defined.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: My sense of IEEE is that they don't like the calculus idea of infinity, but more the computation based numerics. If there is no language in the C standard to talk about the mathematical domain that lurks behind everything,
then it would be hard to introduce it without a lot of work. And instead talk about the computer arithmetic domain.<o:p></o:p></p>
<p class="MsoNormal"> Jim: The mathematics is definitely behind it. Like the discussion of poles, and log referring to the mathematical log functions.<o:p></o:p></p>
<p class="MsoNormal"> ^Jim/Jerome/Damian: Follow up on C26 issue 1.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> TS-4 and TS-5 revisions</b><o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3015]<o:p></o:p></p>
<p class="MsoNormal"> Jim: For TS-4, the use of "consider" is not accepted by ISO. The example for scaled_proddiff, we can say "The following computes a fragment of the Clebsch-Gordan calculation as a simplified example." instead.<o:p></o:p></p>
<p class="MsoNormal"> Jim: For augmented arithmetic, an example has moved to 7.2. This makes it a more ISO conforming way of referring to the example.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> C26 issues</b><o:p></o:p></p>
<p class="MsoNormal"> Issues list<o:p></o:p></p>
<p class="MsoNormal"> See <a href="https://wiki.edg.com/pub/CFP/WebHome/C26C.HTM">https://wiki.edg.com/pub/CFP/WebHome/C26C.HTM</a><o:p></o:p></p>
<p class="MsoNormal"> See [CFP 2992, 2994, 3003, 3005 and follow ups]<o:p></o:p></p>
<p class="MsoNormal"> Jim: CFP3003 should be added to the issues list.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP3003 to the issues list.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: For CFP3006, Vincent has better words for inputs.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: This would change the "correctly rounded" with respect to inputs.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes, correct. We'd have to do that too.<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Draft up changes to incorporate CFP3006.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: Similar for CFP3007. This issue there is he is saying infinity is a floating-point number, but it is not, at least how we have defined it.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP3007 to the C26 issues list.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Issue 1: In progress (Jerome's item).<o:p></o:p></p>
<p class="MsoNormal"> Issue 3: Jim: I have this as no need for change and closed.<o:p></o:p></p>
<p class="MsoNormal"> Issue 4: Jim: Have a draft proposal for this. Action item.<o:p></o:p></p>
<p class="MsoNormal"> Issue 9: Jim: We decided we could close this.<o:p></o:p></p>
<p class="MsoNormal"> Issue 17: Jim: Have a draft proposal for this. Action item.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: Propose we look at 11 and 14 next.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Imaginary types<o:p></o:p></p>
<p class="MsoNormal"> See [N3206, CFP 2979, CFP 2997 and follow ups]<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Annex G complex functions<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3018, 3019, 3032, and follow ups]<o:p></o:p></p>
<p class="MsoNormal"> Damian: Noticed some inconsistencies in Annex G.<o:p></o:p></p>
<p class="MsoNormal"> Damian: CFP3037 has a summary of inconsistencies that are mostly editorial.<o:p></o:p></p>
<p class="MsoNormal"> ^Damian: Get a list of editorial issues in Annex G and send them out for future submission to WG14.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Others?</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Other issues</b><o:p></o:p></p>
<p class="MsoNormal"> IEEE 754 meetings<o:p></o:p></p>
<p class="MsoNormal"> Damian, David, Jerome are attending<span style="color:red"> (Mike attended the first meeting, and will again if requested).</span><o:p></o:p></p>
<p class="MsoNormal"> Fred: IEEE explicitly asked for James Thomas for language input.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Accuracy of mathematical functions<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3002]<o:p></o:p></p>
<p class="MsoNormal"> Fred: Not very good at setting the flags.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>