<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;"><div>Is this suggesting that all floating-point exceptions (except “inexact”) required by Annex F for library functions would, for Annex F implementations, become occurring errors per 7.12.2? This would mean that an Annex F implementation that defines<font face="Courier New"> math_errhandling & MATH_ERRNO</font> to nonzero would have to set <font face="Courier New">errno</font> for all those exceptions. Assuming support for <font face="Courier New">errno</font> is for legacy code, such changes in C would not be helpful. </div><div><br></div><div>- Jim Thomas<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Sep 6, 2025, at 10:07 PM, Fred J. Tydeman <tydeman@tybor.com> wrote:</div><br class="Apple-interchange-newline"><div><div>Should C23 Annex F.10 Mathematics <math.h> and <tgmath.h><br>be updated with:<br><br>"Invalid" being raised is a domain error.<br>"Divide-by-zero" being raised is a pole error.<br>"Overflow" being raised is a range error.<br>"Underflow" being raised is a range error.<br><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></body></html>