<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=Windows-1252">
<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">2024/05/22: 10:00 CT:<o:p></o:p></p>
<p class="MsoNormal"> <b>Attendees</b>: Rajan, Jim, Jerome, Damian, 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/n3258.pdf">https://wiki.edg.com/pub/CFP/WebHome/n3258.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 [CFP 3095] (<a href="http://mailman.oakapple.net/pipermail/cfp-interest/2024-April/003109.html">http://mailman.oakapple.net/pipermail/cfp-interest/2024-April/003109.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"> June 19, 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/Jim: Ask WG14 if a footnote (that we will have provided already) is needed for the CFP 3074 change to 7.1.2#7 saying an exception could still occur for an expression evaluation using the replacement.
<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Make a proposal for WG14 based on CFP 3091.<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"> Jim/Jerome/Damian: Follow up on C26 issue 1 (terms and definitions for math errors).<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"> Fred: Put the text after issue 4 in c26d into issue 5.<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"> 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"> <o:p></o:p></p>
<p class="MsoNormal"> <b>IEEE 754 liaison</b>:<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Scanned a lot of the old IEEE-754 from 1978 and up meeting minutes. Looking for where to put them (Ex. Mike's site?).<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Still waiting for the group to be a real working group (from a study group).<o:p></o:p></p>
<p class="MsoNormal"> Damian: I will go to every 754 meeting.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: I will be more involved but won't make as strong a statement as Damian.<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>C23 integration</b>:<o:p></o:p></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"> Damian: Jens is using a different draft since he is referring to a footnote that is at a different number with regards to the Imaginary removal. Will email him to see what he is using other than N3219.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <b>Carry over action items </b>(Done unless stated otherwise):<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"> Not done.<o:p></o:p></p>
<p class="MsoNormal"><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"> See [CFP 3096, 3097, 3098] Annex F and Annex G - primarily about special cases<o:p></o:p></p>
<p class="MsoNormal"> Damian: Redid it to follow Annex F's style and fix the inconsistencies. Will get David and Fred to review first before opening it up to everyone.<o:p></o:p></p>
<p class="MsoNormal"> Not done.<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)<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Put the text after issue 4 in c26d into issue 5.<o:p></o:p></p>
<p class="MsoNormal"> Still shows the invalid text so not done.<o:p></o:p></p>
<p class="MsoNormal"><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"> Not done.<o:p></o:p></p>
<p class="MsoNormal"><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"> Not done.<o:p></o:p></p>
<p class="MsoNormal"><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"> Tried some changes. But OK with no change.<o:p></o:p></p>
<p class="MsoNormal"> Jerome: Can add a footnote saying that no exception is raised for the evaluation of the replacement alone, but its use in an expression still can raise an exception.<o:p></o:p></p>
<p class="MsoNormal"> ^Rajan/Jim: Ask WG14 if a footnote (that we will have provided already) is needed for the CFP 3074 change to 7.1.2#7 saying an exception could still occur for an expression evaluation using the replacement.<o:p></o:p></p>
<p class="MsoNormal"><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"> <o:p></o:p></p>
<p class="MsoNormal"> Jim: Submit CFP 3058's document to WG14.<o:p></o:p></p>
<p class="MsoNormal"> See [N3242] Proposal for C2Y - problematic use of “correctly rounded".<o:p></o:p></p>
<p class="MsoNormal"> Done. Rajan to present.<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"> Waiting for the C23 final draft.<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"> <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"> <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"> <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"> <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"> <o:p></o:p></p>
<p class="MsoNormal"> Issue 21 (parenthesis): See [CFP 3091].<o:p></o:p></p>
<p class="MsoNormal"> No objections.<o:p></o:p></p>
<p class="MsoNormal"> ^Rajan: Make a proposal for WG14 based on CFP 3091.<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, N3241, N3240, CFP 2979,2997,3018,3019,3032,3053,3055,3083 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> Jim: What should CFP do with this?<o:p></o:p></p>
<p class="MsoNormal"> Damian: Why is this proposal out there?<o:p></o:p></p>
<p class="MsoNormal"> Jim: There was rationale in the original paper. The real reason seems to be lack of implementation.<o:p></o:p></p>
<p class="MsoNormal"> Damian: I thought GCC said it was going to implement it?<o:p></o:p></p>
<p class="MsoNormal"> Jerome: What about LAPACK and scale LAPACK and other consumers? They've been working without implementations for so long but would like it.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes, LAPACK worked around it using real parts.<o:p></o:p></p>
<p class="MsoNormal"> Jim: If Imaginary types are being removed, what role should CFP play in the specification? Ex. Moving operations into the main body of the standard. Usual arithmetic conversions used a common corresponding real type. The rules for
real and complex should be in the main body of the standard since it has nothing to do with 60559 support.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Damians changes work with this too so we need to synchronize it or make sequential changes.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: We should let Jens run with it and only intervene if there are changes that are erroneous with future papers from us to address those issues.<o:p></o:p></p>
<p class="MsoNormal"> Jim: This means we should review the documents he has out for it. N3263 for example. There a lot of changes with no diff on Annex G.<o:p></o:p></p>
<p class="MsoNormal"> Damian: Yes, the whole first page of Annex G seems to have disappeared. A lot of my stuff will not be affected by the change.<o:p></o:p></p>
<p class="MsoNormal"> Jim: We can send proposals after Jens changes take effect.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Annex G:<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 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"> Meaning of 0 < x < infinity<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3046 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> Damian: This has been resolved. Remove from the list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Wording<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3056,3059,3099 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> Close this item as well as it is integrated into the other items.<o:p></o:p></p>
<p class="MsoNormal"> Damian: "type name" is used before it is defined. 6.2.5#15 says complex types, but not what the type names are. Clause 16 then talks about type name without a definition.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: 6.2.1#8 does talk about type names being a regular English term.<o:p></o:p></p>
<p class="MsoNormal"> Jim: I don't see it. It is not written at that level of formality. A type has many aspects, one of which is the name. Nothing confusing here or any problem.<o:p></o:p></p>
<p class="MsoNormal"> Damian: Maybe I am overcomplicating it. OK with leaving it as is.<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"> None.<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"> Typeface inconsistency:<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3076,3094].<o:p></o:p></p>
<p class="MsoNormal"> Jim: Already sent a note to JeanHeyd about this. No response.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> frexp and double-double underflow<o:p></o:p></p>
<p class="MsoNormal"> See [CFP 3100 and follow ups].<o:p></o:p></p>
<p class="MsoNormal"> Keep on the agenda.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>