aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc b/libstdc++-v3/testsuite/18_support/numeric_limits/traps.cc
index ecfbdeb..4963b90 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.