From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
GCC Development <gcc@gcc.gnu.org>, X86 ML <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: typeof and operands in named address spaces
Date: Thu, 5 Nov 2020 10:51:08 +0100 [thread overview]
Message-ID: <20201105095108.GY3788@tucnak> (raw)
In-Reply-To: <CAFiYyc02u8169K8jSxj8wBnfurXnr118sdR6Le1w8GwHkCauGQ@mail.gmail.com>
On Thu, Nov 05, 2020 at 10:45:59AM +0100, Richard Biener wrote:
> Well, I think we should fix typeof to not retain the address space. It's
> probably our implementation detail of having those in TYPE_QUALS
> that exposes the issue and not standard mandated.
>
> The rvalue trick is to avoid depending on a "fixed" GCC.
>
> Joseph should know how typeof should behave here.
For other qualifiers like const it has been discussed recently in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97702
and I think the address space qualifiers should work the same as others.
Jakub
next prev parent reply other threads:[~2020-11-05 9:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 18:31 Uros Bizjak
2020-11-05 7:26 ` Richard Biener
2020-11-05 8:56 ` Uros Bizjak
2020-11-05 9:36 ` Alexander Monakov
2020-11-05 10:33 ` Uros Bizjak
2020-11-05 11:38 ` Alexander Monakov
2020-11-05 12:00 ` Uros Bizjak
2020-11-05 12:14 ` Alexander Monakov
2020-11-05 12:24 ` Richard Biener
2020-11-05 12:32 ` Uros Bizjak
2020-11-05 12:35 ` Uros Bizjak
2020-11-05 13:22 ` Alexander Monakov
2020-11-05 13:39 ` Alexander Monakov
2020-11-05 13:46 ` Uros Bizjak
2020-11-05 12:26 ` Uros Bizjak
2020-11-05 15:27 ` Andy Lutomirski
2020-11-05 11:03 ` Uros Bizjak
2020-11-05 9:45 ` Richard Biener
2020-11-05 9:51 ` Jakub Jelinek [this message]
2020-11-09 12:47 ` Peter Zijlstra
2020-11-09 19:38 ` Segher Boessenkool
2020-11-09 19:50 ` Nick Desaulniers
2020-11-10 7:57 ` Peter Zijlstra
2020-11-10 18:42 ` Nick Desaulniers
2020-11-10 20:11 ` Peter Zijlstra
2020-11-12 0:40 ` Segher Boessenkool
2020-11-12 0:47 ` Segher Boessenkool
2020-11-10 7:52 ` Peter Zijlstra
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=20201105095108.GY3788@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=luto@amacapital.net \
--cc=richard.guenther@gmail.com \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.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).