<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">We discussed this thread at the March 2024 CFP meeting, nominally as Issue 5 in the list in C26D (<a href="https://wiki.edg.com/pub/CFP/WebHome/c26d.htm">https://wiki.edg.com/pub/CFP/WebHome/c26d.htm</a>). By my count, there are four issues in the thread that need response. Rajan took an action item to draft fixes for two of them, which he did in<div><br></div><div>o<span class="Apple-tab-span" style="white-space:pre"> </span>[Cfp-interest 3045] Action item for Rajan: C26 issue 5 version 2</div><div><br></div><div>However, no action items were assigned for two others where I believe we had agreement. Suggested action items follow.</div><div><br></div><div><div><blockquote type="cite"><div>On Mar 8, 2024, at 4:21 PM, Jim Thomas <jaswthomas@sbcglobal.net> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Do we intend for the evaluation of any object-like macros defined in Clause 7 or Annexes F, G, H or K to raise a floating-point exception at execution time? If not, we might add that as a requirement in 7.1.2. See 7.1.2 #7 (in n3219).</span></div></blockquote><div><br></div><div>Suggested action item: Write a proposal for the following change: </div><div><br></div>After 7.1.2 #7, insert the paragraph</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div>The evaluation of the replacement for an object-like macro described in this clause or Annexes F, Annex G, Annex H, or Annex K shall not raise a floating-point exception.</div></div></blockquote><div><br></div><div>This addresses original Issue 5. The sentence follows the form of a similar one in 7.1.2 #7.</div><div><br></div><div><blockquote type="cite"><div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><blockquote type="cite"><div>On Feb 11, 2024, at 9:58 AM, Fred J. Tydeman <<a href="mailto:tydeman@tybor.com">tydeman@tybor.com</a>> wrote:</div><br class="Apple-interchange-newline"><div><div>On Wed, 7 Feb 2024 19:37:46 +0000 Rajan Bhakta wrote:<br><blockquote type="cite"><br> Jim: Are there any <math.h> macros with this issue? Should words be added to an introduction section in <float.h>?<br> ^Fred: Look into.<br></blockquote><br><math.h> macros that should not raise exceptions when evaluated:<br><br>HUGE_VAL, HUGE_VALF, HUGE_VALL, HUGE_VAL_D*<br>INFINITY, DEC_INFINITY<br>NAN, DEC_NAN<br><br><br>Aside: Should 7.12.1#5 (overflow) mention HUGE_VAL_D*?<br></div></div></blockquote><div><br></div></div></div></div></blockquote><blockquote type="cite"><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div>Right. Perhaps change </div><div><br></div></div><blockquote style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; margin: 0px 0px 0px 40px; border: medium; padding: 0px;">returns the value of the macro HUGE_VAL, HUGE_VALF, or HUGE_VALL according to the return type</blockquote><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><br></div><div>to</div><div><br></div></div><blockquote style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; margin: 0px 0px 0px 40px; border: medium; padding: 0px;"><div>returns the value of the macro HUGE_VAL suffixed according to the return type</div><div><br></div></blockquote><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">which would cover the macros in Annex H too.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"></blockquote><div><br></div><div><div>Suggested action item: Write a proposal for the following change.</div><div><br></div><div>In 7.12.1 #5, change</div><div><br></div></div></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div><div><div>… the function returns the value of the macro <b>HUGE_VAL</b>, <b>HUGE_VALF</b>, or <b>HUGE_VALL</b> according to the return type ...</div></div></div></div></div></blockquote><div><div><div><div><div><br></div><div>to</div><div><br></div><div><div><blockquote style="margin: 0px 0px 0px 40px; border: medium; padding: 0px;"><div><div><div><div>… the function returns the value of the macro <b>HUGE_VAL</b> suffixed according to the return type ...</div></div></div></div></blockquote><div><div><div><div></div></div></div></div></div></div></div><blockquote type="cite"><div></div></blockquote></div><div><br></div><blockquote type="cite"><div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><div><div><br></div></div><blockquote type="cite"><div><div><br>SNAN macro "requirement" is in a Recommended practice in F.2.1.<br></div></div></blockquote><div><br></div>I think it's F.2.2 in n3219. It doesn't use “shall” or a form of “require”. Are you interpreting “raises” (in recommended practice) as a requirement?</div><div><br><blockquote type="cite"><div><div><br>FLTn_SNAN, DECn_SNAN, FLTnx_SNAN, DECnx_SNAN in H.3#6<br>HUGE_VAL_Fn, HUGE_VAL_Dn, HUGE_VAL_Fnx, HUGE_VAL_Dnx in H.11.1<br></div></div></blockquote></div></div></div></blockquote><div><br></div>I believe we decided no followup is needed for this issue, unless a problem is identified.<br><blockquote type="cite"><div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><blockquote type="cite"><div><div><br>Aside: 5.2.4.2.2#22 mentions SNAN for translation time initializer,<br>while H.3#6 mentions static or thread storage duration.<br></div></div></blockquote><div><br></div><div>Good catch. I think it’s 5.2.5.3.2#28 in n3219. Is there any reason not to use the words in H.3#6 in both places? </div></div></div></div></blockquote><div><br></div><div><div><div><div>This is one of the issues Rajan addressed in [Cfp-interest 3045]. In the meantime, Fred added this issue as new Issue 20 in C26D.</div><div><br></div><div>During the CFP discussion another issue arose about the specification of initialization with SNAN macros, namely that "an optional unary <b>+</b> or <b>-</b> operator followed by a signaling NaN macro” might suggest erroneously that a unary operator is required. This is the second issue Rajan addressed in [Cfp-interest 3045].</div><div><br></div></div></div></div><div><div><div>- Jim Thomas</div><div><br></div></div></div><blockquote type="cite"><div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><div><br></div><div>- Jim Thomas</div><div><br></div><blockquote type="cite"><div><div><br><br>---<br>Fred J. Tydeman Tydeman Consulting<br>tydeman@tybor.com Testing, numerics, programming<br>+1 (702) 608-6093 Vice-chair of INCITS/C (ANSI "C")<br>Sample C17+FPCE tests: http://www.tybor.com<br>Savers sleep well, investors eat well, spenders work forever.<br><br>_______________________________________________<br>Cfp-interest mailing list<br>Cfp-interest@oakapple.net<br>http://mailman.oakapple.net/mailman/listinfo/cfp-interest<br></div></div></blockquote></div><br></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Cfp-interest mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><a href="mailto:Cfp-interest@oakapple.net" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Cfp-interest@oakapple.net</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">http://mailman.oakapple.net/mailman/listinfo/cfp-interest</a></div></blockquote></div><br></div></body></html>