On Wed, Mar 19, 2025 at 11:29:55PM +0000, Jonathan Wakely wrote:
> libstdc++-v3/ChangeLog:
>
> * include/bits/locale_facets_nonio.tcc (time_put::do_put): Fix
> typo in comment.
Another one, committed as obvious.
2025-03-20 Jakub Jelinek <ja...@redhat.com>
* testsuite/18_support/numeric_limits/traps.cc (main): Fix comment
typo.
--- libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc.jj
2025-01-02 20:54:32.945118626 +0100
+++ libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc 2025-03-20
00:49:52.935180684 +0100
@@ -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.
Jakub
