From: Joseph Myers <joseph@codesourcery.com>
To: Raoni Fassina Firmino <raoni@linux.ibm.com>
Cc: Richard Biener <rguenther@suse.de>, <jakub@redhat.com>,
<segher@kernel.crashing.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v5] rtl: builtins: (not just) rs6000: Add builtins for fegetround, feclearexcept and feraiseexcept [PR94193]
Date: Wed, 4 Nov 2020 21:06:02 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2011042105050.750942@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20201104151049.psotxu7xarcxmv5g@work-tp>
On Wed, 4 Nov 2020, Raoni Fassina Firmino via Gcc-patches wrote:
> IMHO, It seems like it is not necessary if there not a libc that have
> different values for the FE_* macros. I didn't check other archs, but if
> is the case for some other arch I think it could be changed if and when
> some other arch implements expands for these builtins.
SPARC is the case I know of where the FE_* values vary depending on target
libc (see the SPARC_LOW_FE_EXCEPT_VALUES target macro).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-04 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 23:12 Raoni Fassina Firmino
2020-11-04 9:35 ` Richard Biener
2020-11-04 15:10 ` Raoni Fassina Firmino
2020-11-04 21:06 ` Joseph Myers [this message]
2020-11-17 22:19 ` Jeff Law
2020-11-18 7:31 ` Richard Biener
2020-11-18 12:38 ` Segher Boessenkool
2020-11-18 21:45 ` Jeff Law
2021-01-07 14:20 ` Raoni Fassina Firmino
2020-11-17 22:23 ` Jeff Law
2021-01-07 14:20 ` Raoni Fassina Firmino
2021-01-14 17:40 ` Segher Boessenkool
2020-11-04 21:20 ` Joseph Myers
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=alpine.DEB.2.22.394.2011042105050.750942@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=raoni@linux.ibm.com \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.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).