<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"> <b>Attendees</b>:<o:p></o:p></p>
<p class="MsoNormal"> Rajan, Jim, Joshua, Mike, David H, Damian<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> New agenda items:<o:p></o:p></b></p>
<p class="MsoNormal"><b> </b>See current agenda at https://wiki.edg.com/pub/CFP/WebHome/n3169.pdf<b><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>Previous meeting notes:</b><o:p></o:p></p>
<p class="MsoNormal"> See CFP2879 (http://mailman.oakapple.net/pipermail/cfp-interest/2023-August/002893.html).<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"> October 18, 2023, 4PM UTC (only if needed based on WG14 discussion)<o:p></o:p></p>
<p class="MsoNormal"> November 8, 2023, 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"> All: Notify Rajan before the October 16th of any known implementations of the proposed TS part 4 or 5.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Update slide deck with typo (Ex. slide 17 should TS-5 instead of TS-4) and formatting fixes (Ex. subscript for the pi, qi's in the sumProduct operation descriptions)<o:p></o:p></p>
<p class="MsoNormal"> Jim: Change TS-4 page 12, line 1, "As for other" -> "Like other".<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 1, nowhere else in the C standard are pole errors listed as a "shall", just as "may". This could be a problem for the proposed change.<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 2, the problem may not be an issue as it seems to be clear what is the expected result.<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 6, consider explicit definitions instead of implicit references.<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 8, hyphenate floating-point.<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 13, mention "long double" in the issue text. Ex. "Annex F and long double including double-double needs to be clarified."<o:p></o:p></p>
<p class="MsoNormal"> Rajan: C26B Issues 12, 14, need CFP messages. Write some up and send them to the list.<o:p></o:p></p>
<p class="MsoNormal"> Mike: Ask Michel about CFP2899.<o:p></o:p></p>
<p class="MsoNormal"> Jim/David: Check IEEE-754 if there is a similar issue to CFP2899.<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"> [Cfp-interest 2799] Attn WG 14, question about atomic_fetch_* and floating point re: [isocpp-lib- ext] P0493 Atomic max/min<o:p></o:p></p>
<p class="MsoNormal"> - No update/responses yet.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> C23/WG14:<o:p></o:p></b></p>
<p class="MsoNormal"> C2X working draft N3149 (for CFP only)<o:p></o:p></p>
<p class="MsoNormal"> https://wiki.edg.com/pub/CFP/WebHome/N3149.pdf<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Next WG14 meeting: October 16-20, 2023.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: All: Notify Rajan before the October 16th of any known implementations of the proposed TS part 4 or 5.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Group liaison with IEEE 754 needed.<o:p></o:p></p>
<p class="MsoNormal"> David H will be a part of the 754 revision via email review. Mike may do the same, and drop off this group after C23. David H believes the same.<o:p></o:p></p>
<p class="MsoNormal"> Damian may attend. May do WG14.<o:p></o:p></p>
<p class="MsoNormal"> Joshua is not planning on it. But will attend WG14 meetings.<o:p></o:p></p>
<p class="MsoNormal"> Rajan will attend WG14 meetings. Likely Fred as well.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> Carry-over action items results:<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 results (from previous meeting):<o:p></o:p></b></p>
<p class="MsoNormal"> Jim: Make the slide deck C names in a different typeface (fixed width font). See N3165 2023/09/05 Thomas, TS 18661 revisions slide deck<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Jim: Update slide deck with typo (Ex. slide 17 should TS-5) and formatting fixes (Ex. subscript for the pi, qi's in the sumProduct operation descriptions)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Part 4: Typo fix: Change for page 2 line 6: clause 2 -> clause 4.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Part 4: For the change to page 3, line 13 and page 10 line 28: Say the fN and fNx suffixes are there only when the TYPES macro is defined.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Part 4: Page 10, line 27: Change "As for other IEC 60559 operations" to "As with other ..."
<o:p></o:p></p>
<p class="MsoNormal"> Jim: The two "with"s if this change was made seems wrong. So left it as is.<o:p></o:p></p>
<p class="MsoNormal"> David: We did discuss it last time and it should be changed. Perhaps say "rounding includes gradual" or "rounding incorporates gradual" or ", underflow is gradual."<o:p></o:p></p>
<p class="MsoNormal"> Jim: This is not about exceptions.<o:p></o:p></p>
<p class="MsoNormal"> Joshua: Can say "Like other" or "Like with other" instead of "As for other".<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Jim: Change TS-4 page 12, line 1, "As for other" -> "Like other".<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Part 5: Typo fix: Change for page 2 line 9: clause 2 -> clause 4.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Part 5: Page 20, line 14 fix should be for Page 20 line 18.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Rajan: Validate the scaled reduction example compiles.<o:p></o:p></p>
<p class="MsoNormal"> Result: Augmented arithmetic example: Typo in the w assignment: v,t -> v.t<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Scaled reduction example: Put "int i;" into the for loop clause 1 in the code instead of a separate declaration.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> David: Augmented arithmetic example: Get the values for a* and b* in the initialization.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Jim: Augmented arithmetic example: Put the last (sh/st) assignment into two lines.<o:p></o:p></p>
<p class="MsoNormal"> Done.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> N3163 2023/09/05 Thomas, TS 18661-4 revision draft<o:p></o:p></p>
<p class="MsoNormal"> N3164 2023/09/05 Thomas, TS 18661-5 revision draft<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> Issues for C2Y - Only clarifying what might be on the list of what might be in a future revision of the standard, nothing to do with the current revision or balloted document:<o:p></o:p></b></p>
<p class="MsoNormal"> See future issues list at https://wiki.edg.com/pub/CFP/WebHome/C26B.HTM<o:p></o:p></p>
<p class="MsoNormal"> Issue 1:<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: C26B Issue 1, nowhere else in the C standard are pole errors listed as a "shall", just as "may". This could be a problem for the proposed change.<o:p></o:p></p>
<p class="MsoNormal"> Issue 2:<o:p></o:p></p>
<p class="MsoNormal"> David: Yes, this is true, it was a problem in IEEE. It was supposed to be a bit operation, but infinity was a natural result.<o:p></o:p></p>
<p class="MsoNormal"> Jim: We can answer the question that it is an overflow (see 7.12.1#5), but not required since nextafter's description does not fit the range error conditions listed there (see 7.12.11.3#2).<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: For C26B Issue 2, the problem may not be an issue as it seems to be clear what is the expected result.<o:p></o:p></p>
<p class="MsoNormal"> Issue 6:<o:p></o:p></p>
<p class="MsoNormal"> Jim: Not a good thing to implicitly define them through a reference. We should explicitly do so.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: C26B Issue 6, consider explicit definitions instead of implicit references.<o:p></o:p></p>
<p class="MsoNormal"> Issue 7:<o:p></o:p></p>
<p class="MsoNormal"> Jim: It is not in the user space. It is reserved only if you include complex.h.<o:p></o:p></p>
<p class="MsoNormal"> Issue 8:<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: C26B Issue 8, hyphenate floating-point.<o:p></o:p></p>
<p class="MsoNormal"> Issue 13:<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Fred: C26B Issue 13, mention "long double" in the issue text. Ex. "Annex F and long double including double-double needs to be clarified."<o:p></o:p></p>
<p class="MsoNormal"> Issue 14:<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Rajan: C26B Issues 12, 14, need CFP messages. Write some up and send them to the list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> N3159 2023/07/28 Thomas, August 2023 CFP teleconference agenda<o:p></o:p></p>
<p class="MsoNormal"> Jim: The floating vs floating-point item was not added to the list.<o:p></o:p></p>
<p class="MsoNormal"> OK with adding this to the future issues list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> %a/%A formatting. See CFP2888 and follow ons.<o:p></o:p></p>
<p class="MsoNormal"> OK with adding this to the future issues list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Definitions of *_DECIMAL_DIG and DECIMAL_DIG. See CFP2899.<o:p></o:p></p>
<p class="MsoNormal"> Mike: Run this by Michel Hack as well.<o:p></o:p></p>
<p class="MsoNormal"> Jim: We ask this to 754 as well.<o:p></o:p></p>
<p class="MsoNormal"> Mike: Can post this to their list which Michel is following.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Mike: Ask Michel about CFP2899.<o:p></o:p></p>
<p class="MsoNormal"> ^AI: Jim/David: Check 754 if there is a similar issue to CFP2899.<o:p></o:p></p>
<p class="MsoNormal"> OK with adding this to the future issues list.<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"> Mail troubles See [Cfp-interest 2889]<o:p></o:p></p>
<p class="MsoNormal"> Seems to be working.<o:p></o:p></p>
<p class="MsoNormal"> All: Check to ensure that the archives list all emails sent by them during the period in question.: Rajan, Jim, Joshua, Mike, David H, Damian,
<o:p></o:p></p>
</div>
</body>
</html>