<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;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@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="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"> <b>Attendees</b>: Rajan, Jim, Fred, Jerome, Ted Johnson (HPE), David H., Damian,
<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:<o:p></o:p></b></p>
<p class="MsoNormal"> See [CFP 3041] (<a href="https://mailman.oakapple.net/pipermail/cfp-interest/2024-March/003055.html">https://mailman.oakapple.net/pipermail/cfp-interest/2024-March/003055.html</a>).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Next Meeting(s):<o:p></o:p></b></p>
<p class="MsoNormal"> May 22, 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:<o:p></o:p></b></p>
<p class="MsoNormal"> Jim/Jerome/Damian: Follow up on C26 issue 1. - (Carry over).<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. - (Carry over).<o:p></o:p></p>
<p class="MsoNormal"> Fred: Put the text after issue 4 in c26d into issue 5. - Done.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: C26: Issue 1: Revamp to remove the "may" for negative errors.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Create a C26 issue to clear up 7.12.1#1 to ensure SIGFPE is not interpreted as being allowed for any clause 7 functions.<o:p></o:p></p>
<p class="MsoNormal"> Rajan/Jim: Look to reword CFP 3074 change to 7.1.2#7 to avoid an implication you cannot signal if the replacement is part of a larger expression.<o:p></o:p></p>
<p class="MsoNormal"> Jim: C26 Issue 19: Add to the changes for 7.24.1.6 the terms "decimal form" and "hexadecimal form" to paragraph 3's bullets 1 and 2 respectively to make it clear what the changes in paragraph 4 refer to. Also do the changes for issue
19 problems 1 and 2.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Submit CFP 3058's document 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:<o:p></o:p></b></p>
<p class="MsoNormal"> None.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> IEEE 754 liaison:<o:p></o:p></b></p>
<p class="MsoNormal"> David: Moving to have a working group and moving to the next level in IEEE for approval to create it. Gave "Scope" and "Policies and Procedures draft" for IEEE approval. The MSC will appoint a temporary chair where the working group
elects its own real chair and other things like that. Will be looking at the long list of errata and maybe more.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: A lot of work to get new issues on the table.<o:p></o:p></p>
<p class="MsoNormal"> Damian: A lot of discussion.<o:p></o:p></p>
<p class="MsoNormal"> David: Good chance of substantial revisions. Some not upwards compatible. The arithmetic specialists have come back as well (since dropping off after 1985) with specific proposals.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Expecting a lot of correctly rounded elementary functions.<o:p></o:p></p>
<p class="MsoNormal"> Jim: I heard there was some discussion about small formats. Is that serious or going elsewhere?<o:p></o:p></p>
<p class="MsoNormal"> Damian: I know 16-bits are going to make an appearance. Whether 8-bit does, I don't know.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> C++ liaison:<o:p></o:p></b></p>
<p class="MsoNormal"> None.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> C23 integration<o:p></o:p></b></p>
<p class="MsoNormal"> Next WG14 meeting:<o:p></o:p></p>
<p class="MsoNormal"> June 10-14, Virtual. Mailing deadline is one month before the meeting.<o:p></o:p></p>
<p class="MsoNormal"><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"> DIS ballot draft review:<o:p></o:p></p>
<p class="MsoNormal"> See [CFP3038].<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b> Carry over action items<o:p></o:p></b></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 </b>(Done unless stated otherwise)<b><o:p></o:p></b></p>
<p class="MsoNormal"> Rajan: Send the WG14 editorial comments from CFP to CFP.<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3038].<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"> See [CFP 3042,3045].<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"> See [N3233].<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"> See [N3232].<o:p></o:p></p>
<p class="MsoNormal"> ^Jim/Jerome/Damian: Follow up on C26 issue 1. - Not complete (carry over).<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3092].<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP3003 to the issues list.<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3062].<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP3007 to the C26 issues list.<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3062].<o:p></o:p></p>
<p class="MsoNormal"> Jim: Draft up changes to incorporate CFP3006.<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3058].<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. - Not done (carry over).<o:p></o:p></p>
<p class="MsoNormal"> Damian: Jim and Jerome have looked over some of the questions. Will send it to Jim before sending it to the wider group. Made Annex G match the style of Annex F.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> TS-4 and TS-5 revisions<o:p></o:p></b></p>
<p class="MsoNormal"> See [CFP 3015].<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Ballot is out.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> C26 issues<o:p></o:p></b></p>
<p class="MsoNormal"> Issues list<o:p></o:p></p>
<p class="MsoNormal"> See <a href="https://wiki.edg.com/pub/CFP/WebHome/c26d.htm">
https://wiki.edg.com/pub/CFP/WebHome/c26d.htm</a><o:p></o:p></p>
<p class="MsoNormal"> Rajan: Need to fix the text after issue 4 that is outside any issue box.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Will fix it.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: Put the text after issue 4 in c26d into issue 5. - Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Issue 1 (terms and definitions for math errors): See [CFP 2994,3016,3043,3064,3092 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Instead of pole error, say divide-by-zero error.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Why not have gamma of negative zero be a domain error.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: "May occur" is the language in other places in the standard. But in this case it is a domain error and hence should be there.<o:p></o:p></p>
<p class="MsoNormal"> Fred: We should not have "may" there.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: The language of the standard does not use "occurs" as an imparative. I will fix it.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Jerome: C26: Issue 1: Revamp to remove the "may" for negative errors.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Issue with SIGFPE. We'd have to disambiguate it somehow.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Exception and error seems to have differences.<o:p></o:p></p>
<p class="MsoNormal"> Jim: 7.12.1#1 says SIGFPE is not allowed.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: But the "except to reflect ..." part can be read to allow SIGFPE.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes, agreed. This is another separate issue that also applies to overflow.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: Create a C26 issue to clear up 7.12.1#1 to ensure SIGFPE is not interpreted as being allowed for any clause 7 functions.<o:p></o:p></p>
<p class="MsoNormal"> Damian: For proposal 3, and 4 should be clause 7 not clause 1.<o:p></o:p></p>
<p class="MsoNormal"> Jim: For proposal 3, you are adding in domain error.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: For systems that can only show it that way.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: For the definition at the start, the language was changed to the library function vs the original mathematical function base.<o:p></o:p></p>
<p class="MsoNormal"> Fred: The "implementation defined value" is still there.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes, that should not be there given the new definition.<o:p></o:p></p>
<p class="MsoNormal"> Fred: The first line has to be "mathematical" function.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Right, otherwise it can break anyone that did emit a pole error but does not have infinities.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes, this is a technical change that could break implementations.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: IBM HEX gives -HUGE_VAL and ERANGE as the error. This change would break us. For the arithmetic case, we get a floating-point divide exception.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Issue 5,20 (macro exceptions): See [CFP 3045,3074].<o:p></o:p></p>
<p class="MsoNormal"> Rajan's changes: Looks good.<o:p></o:p></p>
<p class="MsoNormal"> CFP 3074: Rajan: The current wording for the 7.1.2#7 may have the "evaluation" part imply (in a hostile reading) that you cannot signal for a case like 5.0 + SNAN since the evaluation of the SNAN is a sub-evaluation of the expression.
<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Rajan,Jim: Look to reword CFP 3074 change to 7.1.2#7 to avoid an implication you cannot signal if the replacement is part of a larger expression.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Break up issue 5 like what was done for issue 19, as per [CFP 3074].<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Issue 18 (stdc_want_iec_60559_ext in math.h): See [CFP 3080].<o:p></o:p></p>
<p class="MsoNormal"> OK.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Issue 19 (strto* and wcsto* wording): See [CFP 3058,3078 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> 1) OK.<o:p></o:p></p>
<p class="MsoNormal"> 2) Jim: For ceil, as given by Joseph, the last part of the returns (after the comma) is unnecessary and should be removed.<o:p></o:p></p>
<p class="MsoNormal"> 3,4) Rajan: Add the "Decimal form" and "Hexadecimal form" to the bullets in paragraph 3 as well to make it unambiguous as to the forms.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Jim: C26 Issue 19: Add to the changes for 7.24.1.6 the terms "decimal form" and "hexadecimal form" to paragraph 3's bullets 1 and 2 respectively to make it clear what the changes in paragraph 4 refer to. Also do the changes
for issue 19 problems 1 and 2.<o:p></o:p></p>
<p class="MsoNormal"> 5,6) ^AI: Jim: Submit CFP 3058's document to WG14.<o:p></o:p></p>
<p class="MsoNormal">^--- Ran out of time ---<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Issue 21 (parenthesis): See [CFP 3091].<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> Imaginary types<o:p></o:p></b></p>
<p class="MsoNormal"> See [N3206, CFP 2979,2997,3018,3019,3032,3053,3055,3083 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"><b> Meaning of 0 < x < infinity<o:p></o:p></b></p>
<p class="MsoNormal"> See [CFP 3046 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"><b> Wording<o:p></o:p></b></p>
<p class="MsoNormal"> See [CFP 3056,3059 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"><b> Others?<o:p></o:p></b></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> Other issues<o:p></o:p></b></p>
<p class="MsoNormal"> Mathematical functions<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3076 and follow ups].<o:p></o:p></p>
</div>
</body>
</html>