From: Richard Biener <richard.guenther@gmail.com>
To: Andrew Carlotti <andrew.carlotti@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] aarch64: Fix pure/const function attributes for intrinsics
Date: Mon, 4 Jul 2022 08:49:59 +0200 [thread overview]
Message-ID: <CAFiYyc1omrUP=6t9wphm6MvNp7py_79tPvyfLseF5Snmh6w-1A@mail.gmail.com> (raw)
In-Reply-To: <Yr8Z2dDTdjfEvCtK@e124511.cambridge.arm.com>
On Fri, Jul 1, 2022 at 5:59 PM Andrew Carlotti <andrew.carlotti@arm.com> wrote:
>
> On Fri, Jul 01, 2022 at 08:42:15AM +0200, Richard Biener wrote:
> > On Thu, Jun 30, 2022 at 6:04 PM Andrew Carlotti via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> > > diff --git a/gcc/config/aarch64/aarch64-builtins.cc b/gcc/config/aarch64/aarch64-builtins.cc
> > > index e0a741ac663188713e21f457affa57217d074783..877f54aab787862794413259cd36ca0fb7bd49c5 100644
> > > --- a/gcc/config/aarch64/aarch64-builtins.cc
> > > +++ b/gcc/config/aarch64/aarch64-builtins.cc
> > > @@ -1085,9 +1085,9 @@ aarch64_get_attributes (unsigned int f, machine_mode mode)
> > > if (!aarch64_modifies_global_state_p (f, mode))
> > > {
> > > if (aarch64_reads_global_state_p (f, mode))
> > > - attrs = aarch64_add_attribute ("pure", attrs);
> > > - else
> > > attrs = aarch64_add_attribute ("const", attrs);
> > > + else
> > > + attrs = aarch64_add_attribute ("pure", attrs);
> >
> > that looks backwards. 'pure' allows read of global memory while
> > 'const' does not. Is
> > aarch64_reads_global_state_p really backwards?
>
> Oh - the thing that's backwards is my understanding of what "pure" and
> "const" mean. Their meanings as GCC function attributes seem to be
> approximately the opposite way round to their meanings in general usage.
I bet GCCs reading is older ;)
Richard.
prev parent reply other threads:[~2022-07-04 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:03 Andrew Carlotti
2022-07-01 6:42 ` Richard Biener
2022-07-01 15:59 ` Andrew Carlotti
2022-07-04 6:49 ` Richard Biener [this message]
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='CAFiYyc1omrUP=6t9wphm6MvNp7py_79tPvyfLseF5Snmh6w-1A@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=andrew.carlotti@arm.com \
--cc=gcc-patches@gcc.gnu.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).