From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Cc: Bruno Haible <bruno@clisp.org>
Subject: [PATCH v2 0/3] Fix fesetexcept/fesetexceptflag on powerpc and x86
Date: Tue, 24 Oct 2023 08:37:13 -0300 [thread overview]
Message-ID: <20231024113716.3911015-1-adhemerval.zanella@linaro.org> (raw)
Bruno has found fesetexcept/fesetexceptflag wrongly raise floating-point
exception flags on x86 and powerpc.
Adhemerval Zanella (2):
powerpc: Do not raise exception traps for fesetexcept/fesetexceptflag
(BZ 30988)
i686: Do not raise exception traps on fesetexcept (BZ 30989)
Bruno Haible (1):
x86: Do not raises floating-point exception traps on fesetexceptflag
(BZ 30990)
math/test-fesetexcept-traps.c | 22 ++++++---
math/test-fexcept-traps.c | 22 ++++++---
sysdeps/i386/fpu/fesetexcept.c | 41 +++++++++++++++--
sysdeps/i386/fpu/fsetexcptflg.c | 58 +++++++++++++++---------
sysdeps/i386/fpu/math-tests-trap-force.h | 29 ++++++++++++
sysdeps/powerpc/fpu/fesetexcept.c | 5 ++
sysdeps/powerpc/fpu/fsetexcptflg.c | 9 +++-
sysdeps/x86_64/fpu/fsetexcptflg.c | 24 ++++++----
8 files changed, 160 insertions(+), 50 deletions(-)
create mode 100644 sysdeps/i386/fpu/math-tests-trap-force.h
--
2.34.1
next reply other threads:[~2023-10-24 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 11:37 Adhemerval Zanella [this message]
2023-10-24 11:37 ` [PATCH v2 1/3] powerpc: Do not raise exception traps for fesetexcept/fesetexceptflag (BZ 30988) Adhemerval Zanella
2023-10-24 11:37 ` [PATCH v2 2/3] i686: Do not raise exception traps on fesetexcept (BZ 30989) Adhemerval Zanella
2023-10-24 13:43 ` Bruno Haible
2023-10-26 18:39 ` Adhemerval Zanella Netto
2023-10-30 15:21 ` Bruno Haible
2023-10-30 16:05 ` Adhemerval Zanella Netto
2023-10-24 11:37 ` [PATCH v2 3/3] x86: Do not raises floating-point exception traps on fesetexceptflag (BZ 30990) Adhemerval Zanella
2023-10-30 15:22 ` Bruno Haible
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=20231024113716.3911015-1-adhemerval.zanella@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bruno@clisp.org \
--cc=libc-alpha@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).