<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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
.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="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<div id="mail-editor-reference-message-container">
<div>
<p class="MsoNormal"> <b>Attendees</b>: Rajan, Jim, Mike, Fred, Jerome Coonen, Joshua, Damian, David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> New agenda items (<a href="https://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda-20231108-update.pdf">https://wiki.edg.com/pub/CFP/WebHome/CFP_meeting_agenda-20231108-update.pdf</a>):<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:<o:p></o:p></b></p>
<p class="MsoNormal"> See CFP2903 (<a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-October/002917.html">http://mailman.oakapple.net/pipermail/cfp-interest/2023-October/002917.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"> December 6, 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"> Jim: Part 4: Add a footnote anchored on something that says "For an example of emulating augmented arithmetic, see <paper on augmented arithmetic emulation from CFP2949>" and add it to the bibliography in part 4.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Fix Issue 2 in C26B "reported by" text to be in the correct column.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP2904 as a reference for C26B issue 12.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP2905 as a reference for C26B issue 14.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP2913 and CFP2918 to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP2947 as a new issue to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Add CFP2888 and follow ons to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Add a footnote to Part 4, Clause 6 when it describes dN for N != 32, 64, 128 to say N = 32, 64, 128 are covered due to them being 60559 types and covered in Annex F.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Review the bibliography in part 4.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Review the bibliography in part 5.<o:p></o:p></p>
<p class="MsoNormal"> Jim: Part 4: Add a subclause to 5 (perhaps 5.4) for reserving prefixes, possibly referring to C 7.33.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Send a note to JeanHeyd and cc Aaron to give CFP's recommendation for fixing the typo in H.2.1: Use "binary digits (bits)" for the first table second row, and "decimal digits" for the second table, second row.<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"> 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"> <o:p></o:p></p>
<p class="MsoNormal"><b> C23/WG14:<o:p></o:p></b></p>
<p class="MsoNormal"> WG14 meeting summary:<o:p></o:p></p>
<p class="MsoNormal"> See CFP2919, CFP2922<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> C2X working draft N3149 (for CFP only)<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://wiki.edg.com/pub/CFP/WebHome/N3149.pdf">
https://wiki.edg.com/pub/CFP/WebHome/N3149.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Next WG14 meeting: January 22-26, 2024.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> Status of C23 integration:<o:p></o:p></p>
<p class="MsoNormal"> See CFP2939, CFP2940<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. Will drop from agenda unless something comes up.<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"> 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"> Done late. See CFP2949.<o:p></o:p></p>
<p class="MsoNormal"> Jim: The paper in the email seems to be useful for this.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Can add this as a footnote anchored on something that says "For an example of emulating augmented arithmetic, see <paper>" and add it to the bibliography in part 4.<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Part 4: Add a footnote anchored on something that says "For an example of emulating augmented arithmetic, see <paper on augmented arithmetic emulation from CFP2949>" and add it to the bibliography in part 4.<o:p></o:p></p>
<p class="MsoNormal"><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"> Done. See CFP2908<o:p></o:p></p>
<p class="MsoNormal"><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"> Done. See review of TS-4 below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <a href="https://wiki.edg.com/pub/CFP/WebHome/C26B.HTM">
https://wiki.edg.com/pub/CFP/WebHome/C26B.HTM</a><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"> Not done.<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"> Not done.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Fix Issue 2 in C26B "reported by" text to be in the correct column.<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"> Not done.<o:p></o:p></p>
<p class="MsoNormal"> Fred: C26B Issue 8, hyphenate floating-point.<o:p></o:p></p>
<p class="MsoNormal"> Not done.<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"> Not done.<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"> Done. See CFP2904, CFP2905.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Vincent's responses were very useful. We can't talk about it here though right now.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP2904 as a reference for C26B issue 12.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP2905 as a reference for C26B issue 14.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Mike: Ask Michel about CFP2899.<o:p></o:p></p>
<p class="MsoNormal"> Done. See CFP2913.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP2913 and CFP2918 to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"><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"> Done. See CFP2947.<o:p></o:p></p>
<p class="MsoNormal"> Jim: This is not a problem in 754 since it says use round to nearest. However C 5.2.4.2.2 has <type>_DIG doesn't say round to nearest which needs to be fixed.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP2947 as a new issue to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> From previous meeting minutes:<o:p></o:p></b></p>
<p class="MsoNormal"> %a/%A formatting. See CFP2888 and follow ons. OK with adding this to the future issues list.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Add CFP2888 and follow ons to the C26B list.<o:p></o:p></p>
<p class="MsoNormal"> Fred: Does this also cover rounding bumping the leading digit above a one?<o:p></o:p></p>
<p class="MsoNormal"> Jim: Yes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b> Review of TS-4 and TS-5 revisions<o:p></o:p></b></p>
<p class="MsoNormal"> See CFP29{17,20,21,24,25,30,32,41,43,44} and follow ons.<o:p></o:p></p>
<p class="MsoNormal"> Part 4 (without the header changes):<o:p></o:p></p>
<p class="MsoNormal"> OK with all the changes except for:<o:p></o:p></p>
<p class="MsoNormal"> Rajan: For the section 6 changes, _Decimal{32,64,128} does not seem to be covered.<o:p></o:p></p>
<p class="MsoNormal"> Jim: They are specified in Annex F since they have to be IEC 60559 types.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Perhaps have a footnote there to make it clear.<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Add a footnote to Part 4, Clause 6 when it describes dN for N != 32, 64, 128 to say N = 32, 64, 128 are covered due to them being 60559 types and covered in Annex F.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Review the bibliography in part 4.<o:p></o:p></p>
<p class="MsoNormal"> Part 5:<o:p></o:p></p>
<p class="MsoNormal"> OK with all the changes.<o:p></o:p></p>
<p class="MsoNormal"> ^Fred: Review the bibliography in part 5.<o:p></o:p></p>
<p class="MsoNormal"> Part 4 (with the header changes):<o:p></o:p></p>
<p class="MsoNormal"> See CFP2946 along with the document.<o:p></o:p></p>
<p class="MsoNormal"> Joshua: Perhaps say the headers here are standard headers in 7.1.2.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: That's in the CFP message.<o:p></o:p></p>
<p class="MsoNormal"> Joshua: OK, was looking at the wrong text.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: No reserved name changes?<o:p></o:p></p>
<p class="MsoNormal"> Jim: Can add a 5.4 for this referring to 7.33.<o:p></o:p></p>
<p class="MsoNormal"> ^Jim: Part 4: Add a subclause to 5 (perhaps 5.4) for reserving prefixes, possibly referring to C 7.33.<o:p></o:p></p>
<p class="MsoNormal"> Otherwise OK with the changes.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: Suggest only one part 4 with everything in it (not one without the headers as well).<o:p></o:p></p>
<p class="MsoNormal"> General agreement.<o:p></o:p></p>
<p class="MsoNormal"> Damian: For CFP2945, it is for 754. Not for C.<o:p></o:p></p>
<p class="MsoNormal"> Jim: You may want to send it to 754.<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"> Editorial fix for H.2.1<o:p></o:p></p>
<p class="MsoNormal"> See CFP2939 and CFP2940.<o:p></o:p></p>
<p class="MsoNormal"> Jim: For decimal, it should be precision in "digits" rather than bits.<o:p></o:p></p>
<p class="MsoNormal"> Damian: Even in binary it should be "digits". Ex. "p, precision in binary digits"<o:p></o:p></p>
<p class="MsoNormal"> Joshua: It was right in the TS. Just wrongly transferred to the C standard.<o:p></o:p></p>
<p class="MsoNormal"> Mike: Binary digits sounds wrong, should keep it.<o:p></o:p></p>
<p class="MsoNormal"> Rajan: But the C standard in 5.2.4.2.2 says digits so we should do the same for it in binary. It has a direct link to that section in the standard that says digits.<o:p></o:p></p>
<p class="MsoNormal"> Mike: Use "binary digits (bits)" for the first table.<o:p></o:p></p>
<p class="MsoNormal"> ^Rajan: Send a note to JeanHeyd and cc Aaron to give CFP's recommendation for fixing the typo in H.2.1: Use "binary digits (bits)" for the first table second row, and "decimal digits" for the second table, second row.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Forum for discussion about implementation<o:p></o:p></p>
<p class="MsoNormal"> See CFP2942.<o:p></o:p></p>
<p class="MsoNormal"> Damian: Got an email from David on this already. (Rajan: See CFP2952)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> IEEE-754 2029<o:p></o:p></p>
<p class="MsoNormal"> See CFP2948.<o:p></o:p></p>
<p class="MsoNormal"> David: Not planning on taking an active role for 2029 since I don't expect to live that long! Planning to participate in the first few study group meetings at least though.<o:p></o:p></p>
<p class="MsoNormal"> Jim: First few meetings may be interesting to see the scope of things that will be covered.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>