public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] manual: Clarify undefined behavior of feenableexcept (BZ 31019)
Date: Tue, 19 Dec 2023 18:35:39 +0000 (GMT)	[thread overview]
Message-ID: <20231219183539.F197F385840D@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e55599e0286655dd5f1f5b48005a17be37cc7f2c

commit e55599e0286655dd5f1f5b48005a17be37cc7f2c
Author: Bruno Haible <bruno@clisp.org>
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 <carlos@redhat.com>

Diff:
---
 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})

                 reply	other threads:[~2023-12-19 18:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231219183539.F197F385840D@sourceware.org \
    --to=azanella@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).