public inbox for
help / color / mirror / Atom feed
* [glibc] manual: Clarify undefined behavior of feenableexcept (BZ 31019)
@ 2023-12-19 18:35 Adhemerval Zanella
  0 siblings, 0 replies; only message in thread
From: Adhemerval Zanella @ 2023-12-19 18:35 UTC (permalink / raw)
  To: glibc-cvs;h=e55599e0286655dd5f1f5b48005a17be37cc7f2c

commit e55599e0286655dd5f1f5b48005a17be37cc7f2c
Author: Bruno Haible <>
Date:   Wed Nov 1 02:10:11 2023 +0100

    manual: Clarify undefined behavior of feenableexcept (BZ 31019)
    Explain undefined behavior of feenableexcept in a special case.
    Reviewed-by: Carlos O'Donell <>

 manual/arith.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/manual/arith.texi b/manual/arith.texi
index fa7110e992..be24c20493 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -1176,6 +1176,12 @@ enabled, the status of the other exceptions is not changed.
 The function returns the previous enabled exceptions in case the
 operation was successful, @code{-1} otherwise.
+Note: Enabling traps for an exception for which the exception flag is
+currently already set (@pxref{Status bit operations}) has unspecified
+consequences: it may or may not trigger a trap immediately.
+@c It triggers a trap immediately on powerpc*, at the next floating-
+@c instruction on i386, and not at all on the other CPUs.
 @end deftypefun
 @deftypefun int fedisableexcept (int @var{excepts})

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-12-19 18:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-19 18:35 [glibc] manual: Clarify undefined behavior of feenableexcept (BZ 31019) Adhemerval Zanella

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).