This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
[PATCH] Remove misleading statement about raising of FE_INVALID (bug 24078)
- From: "Gabriel F. T. Gomes" <gabriel at inconstante dot eti dot br>
- To: <libc-alpha at sourceware dot org>
- Cc: <gromero at linux dot vnet dot ibm dot com>
- Date: Wed, 9 Jan 2019 16:42:23 -0200
- Subject: [PATCH] Remove misleading statement about raising of FE_INVALID (bug 24078)
See bugzilla entry for a longer description.
-- 8< --
In the floating-point comparisons `==' and `<', there is no difference
in behavior when it comes to the raising of FE_INVALID exceptions. This
patch removes, from the manual, a sentence that states otherwise.
[BZ #24078]
* manual/arith.texi (Floating-Point Comparison Functions):
Remove statement about `==' and `!=' not raising floating-point
exceptions.
---
manual/arith.texi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/manual/arith.texi b/manual/arith.texi
index 6ca7902b3d..163ef7ef25 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -1947,9 +1947,7 @@ int v = a < 1.0;
@end smallexample
@noindent
-will raise an exception if @var{a} is NaN. (This does @emph{not}
-happen with @code{==} and @code{!=}; those merely return false and true,
-respectively, when NaN is examined.) Frequently this exception is
+will raise an exception if @var{a} is NaN. Frequently this exception is
undesirable. @w{ISO C99} therefore defines comparison functions that
do not raise exceptions when NaN is examined. All of the functions are
implemented as macros which allow their arguments to be of any
--
2.14.5