From: Jakub Jelinek Date: Thu, 20 Mar 2025 09:36:29 +0000 (+0100) Subject: libstdc++: Fix comment typo X-Git-Tag: basepoints/gcc-16~1088 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d458020e19b686e0d46320e7d26fa876c19965a0;p=thirdparty%2Fgcc.git libstdc++: Fix comment typo Another IEE typo. 2025-03-20 Jakub Jelinek * testsuite/18_support/numeric_limits/traps.cc (main): Fix comment typo. --- diff --git a/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc b/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc index ecfbdeb02da8..4963b90e6d9a 100644 --- a/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc +++ b/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc @@ -48,7 +48,7 @@ int main() For floating points, trapping is a different, more complicated story. If is_iecxxx is true, then division by zero would not trap (infinity). If is_iecxxx is false, we don't know (VAX may trap for - 0/0 -- I have to check). For most cases (i.e. IEE-754), trapping + 0/0 -- I have to check). For most cases (i.e. IEEE-754), trapping for floating points have to do with whether there is a support for signaling NaN. - Gaby.