From: Jakub Jelinek <jakub@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
linux-toolchains@vger.kernel.org, "Uecker,
Martin" <Martin.Uecker@med.uni-goettingen.de>,
"amonakov@ispras.ru" <amonakov@ispras.ru>,
"ubizjak@gmail.com" <ubizjak@gmail.com>,
"luto@kernel.org" <luto@kernel.org>,
Will Deacon <will@kernel.org>
Subject: Re: Re: typeof and operands in named address spaces
Date: Tue, 17 Nov 2020 20:25:30 +0100 [thread overview]
Message-ID: <20201117192530.GA3788@tucnak> (raw)
In-Reply-To: <CAHk-=wh_kn11vXfi2Ns8E4F0GgmUprQtD-=RnU6Eg+N7coY5gw@mail.gmail.com>
On Tue, Nov 17, 2020 at 11:13:52AM -0800, Linus Torvalds wrote:
> > +#define __unqual_typeof(type) typeof( (typeof(type))type )
> that's certainly a much nicer version than the existing pre-processor
> expansion from hell.
It would need to be typeof( (typeof(type)) (type) ) to not be that
constrained on what kind of expressions it accepts as arguments.
Anyway, it won't work with array types at least,
int a[10];
typeof ((typeof (a)) (a)) b;
is an error (in both gcc and clang), while typeof (a) b; will work
(but not drop the qualifiers). Don't know if the kernel cares or not.
Jakub
next prev parent reply other threads:[~2020-11-17 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1605437478.5370.9.camel@med.uni-goettingen.de>
[not found] ` <CAFiYyc1-qtU+4Tj3mkz=c608zeP8feyuD6UyRhQv19qjKjJcvg@mail.gmail.com>
2020-11-16 11:10 ` Re: typeof and operands in named address spaces Peter Zijlstra
2020-11-16 11:23 ` Peter Zijlstra
2020-11-16 12:23 ` Uecker, Martin
2020-11-16 13:07 ` Peter Zijlstra
2020-11-17 19:13 ` Linus Torvalds
2020-11-17 19:25 ` Jakub Jelinek [this message]
2020-11-17 19:31 ` Linus Torvalds
2020-11-17 21:10 ` Will Deacon
2020-11-17 22:15 ` Will Deacon
2020-11-17 21:23 ` Uecker, Martin
2020-11-17 19:47 ` Linus Torvalds
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=20201117192530.GA3788@tucnak \
--to=jakub@redhat.com \
--cc=Martin.Uecker@med.uni-goettingen.de \
--cc=amonakov@ispras.ru \
--cc=gcc@gcc.gnu.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=will@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