From: Paul E Murphy <murphyp@linux.ibm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2] powerpc: Fix __fesetround_inline_nocheck on POWER9+ (BZ 31682)
Date: Mon, 6 May 2024 15:07:08 -0500 [thread overview]
Message-ID: <fd207043-0f64-4451-b841-4c0d4c435e7a@linux.ibm.com> (raw)
In-Reply-To: <20240506170807.1644139-1-adhemerval.zanella@linaro.org>
On 5/6/24 12:07 PM, Adhemerval Zanella wrote:
> The e68b1151f7460d5fa88c3a567c13f66052da79a7 commit changed the
> __fesetround_inline_nocheck implementation to use mffscrni
> (through __fe_mffscrn) instead of mtfsfi. For generic powerpc
> ceil/floor/trunc, the function is supposed to disable the
> floating-point inexact exception enablebbit, however mffscrni
> does not change any exception enable bits.
>
> This patch fixes by reverting the optimization for the
> __fesetround_inline_nocheck.
>
> Checked on powerpc-linux-gnu.
> ---
> sysdeps/powerpc/fpu/fenv_libc.h | 16 +++++-----------
> sysdeps/powerpc/fpu/round_to_integer.h | 6 +++---
> 2 files changed, 8 insertions(+), 14 deletions(-)
>
> diff --git a/sysdeps/powerpc/fpu/fenv_libc.h b/sysdeps/powerpc/fpu/fenv_libc.h
> index f9167056a8..84b53d5d3e 100644
> --- a/sysdeps/powerpc/fpu/fenv_libc.h
> +++ b/sysdeps/powerpc/fpu/fenv_libc.h
> @@ -182,19 +182,13 @@ __fesetround_inline (int round)
> return 0;
> }
>
> -/* Same as __fesetround_inline, however without runtime check to use DFP
> - mtfsfi syntax (as relax_fenv_state) or if round value is valid. */
> +/* Same as __fesetround_inline, but it also disable the floating-point
> + exceptions (bits 56:63 - VE, OE, UE, ZE, XE, NI, and RN). It does
> + not check if ROUND is a valid value. */
This function will only disable XE (assuming NI is always 0). mtfsfi
operates on 4 bit fields.
> static inline void
> -__fesetround_inline_nocheck (const int round)
> +__fesetround_inline_disable_except (const int round)
> {
> -#ifdef _ARCH_PWR9
> - __fe_mffscrn (round);
> -#else
> - if (__glibc_likely (GLRO(dl_hwcap2) & PPC_FEATURE2_ARCH_3_00))
> - __fe_mffscrn (round);
> - else
> - asm volatile ("mtfsfi 7,%0" : : "n" (round));
> -#endif
> + asm volatile ("mtfsfi 7,%0" : : "n" (round));
> }
>
> #define FPSCR_MASK(bit) (1 << (31 - (bit)))
> diff --git a/sysdeps/powerpc/fpu/round_to_integer.h b/sysdeps/powerpc/fpu/round_to_integer.h
> index b68833640f..c053719530 100644
> --- a/sysdeps/powerpc/fpu/round_to_integer.h
> +++ b/sysdeps/powerpc/fpu/round_to_integer.h
> @@ -42,14 +42,14 @@ set_fenv_mode (enum round_mode mode)
> switch (mode)
> {
> case CEIL:
> - __fesetround_inline_nocheck (FE_UPWARD);
> + __fesetround_inline_disable_except (FE_UPWARD);
> break;
> case FLOOR:
> - __fesetround_inline_nocheck (FE_DOWNWARD);
> + __fesetround_inline_disable_except (FE_DOWNWARD);
> break;
> case TRUNC:
> case ROUND:
> - __fesetround_inline_nocheck (FE_TOWARDZERO);
> + __fesetround_inline_disable_except (FE_TOWARDZERO);
> break;
> case NEARBYINT:
> /* Disable FE_INEXACT exception */
next prev parent reply other threads:[~2024-05-06 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 17:07 Adhemerval Zanella
2024-05-06 18:46 ` Peter Bergner
2024-05-06 20:07 ` Paul E Murphy [this message]
2024-05-07 12:02 ` Adhemerval Zanella Netto
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=fd207043-0f64-4451-b841-4c0d4c435e7a@linux.ibm.com \
--to=murphyp@linux.ibm.com \
--cc=adhemerval.zanella@linaro.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).