public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: Manjunath Matti <mmatti@linux.ibm.com>, libc-alpha@sourceware.org
Cc: rajis@linux.ibm.com, Carl Love <cel@linux.ibm.com>
Subject: Re: [PATCH] [powerpc] fegetenv_and_set_rn now uses the builtins provided by GCC.
Date: Wed, 18 Oct 2023 20:47:23 -0500	[thread overview]
Message-ID: <cf0d35a7-5afb-4b8e-b3d2-b515043e0983@linux.ibm.com> (raw)
In-Reply-To: <20230923154951.3783611-1-mmatti@linux.ibm.com>

On 9/23/23 10:49 AM, Manjunath Matti wrote:
> GCC version 14 onwards supports builtins as __builtin_set_fpscr_rn
> which now returns the FPSCR fields in a double. This feature is
> available on Power9 when the __SET_FPSCR_RN_RETURNS_FPSCR__ macro
> is defined.

The last sentence is not completely correct, since the feature is available
on pre-Power9 cpus too.  The first sentence could be worded a little better
too.  How about:

GCC version 14 onwards supports the __builtin_set_fpscr_rn built-in, 
which now returns the FPSCR fields in a double. This feature is
available when the __SET_FPSCR_RN_RETURNS_FPSCR__ macro is defined.

Peter



  parent reply	other threads:[~2023-10-19  1:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 15:49 Manjunath Matti
2023-09-27 16:56 ` Adhemerval Zanella Netto
2023-10-19  1:47 ` Peter Bergner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-12  8:27 Manjunath Matti
2023-09-12 13:27 ` Adhemerval Zanella Netto
2023-09-20 11:28   ` Manjunath S Matti
2023-09-20 13:33     ` Adhemerval Zanella Netto
2023-10-19  1:25     ` Peter Bergner

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=cf0d35a7-5afb-4b8e-b3d2-b515043e0983@linux.ibm.com \
    --to=bergner@linux.ibm.com \
    --cc=cel@linux.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mmatti@linux.ibm.com \
    --cc=rajis@linux.ibm.com \
    /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).