public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de>
Cc: "richard.guenther@gmail.com" <richard.guenther@gmail.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"ubizjak@gmail.com" <ubizjak@gmail.com>,
	"will@kernel.org" <will@kernel.org>,
	"luto@kernel.org" <luto@kernel.org>,
	"amonakov@ispras.ru" <amonakov@ispras.ru>,
	"linux-toolchains@vger.kernel.org"
	<linux-toolchains@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: Re: Re: typeof and operands in named address spaces
Date: Mon, 16 Nov 2020 14:07:26 +0100	[thread overview]
Message-ID: <20201116130726.GD3121392@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <d6713ba83e91046f32cc1db93277e2f627d04c34.camel@med.uni-goettingen.de>

On Mon, Nov 16, 2020 at 12:23:17PM +0000, Uecker, Martin wrote:

> > > > Another way to drop qualifiers is using a cast. So you
> > > > can use typeof twice:
> > > > 
> > > > typeof((typeof(_var))_var) tmp__;
> > > > 
> > > > This also works for non-scalars but this is a GCC extension.
> 
> (That casts drop qualifiers is standard C. The extensions
> are 'typeof' and that casts can be used for non-scalar types.)

Ah, I'll clarify. Thanks!

  reply	other threads:[~2020-11-16 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 10:51 Uecker, Martin
2020-11-16  9:11 ` Richard Biener
2020-11-16 11:10   ` Peter Zijlstra
2020-11-16 11:23     ` Peter Zijlstra
2020-11-16 12:23     ` Uecker, Martin
2020-11-16 13:07       ` Peter Zijlstra [this message]
2020-11-17 19:13     ` Linus Torvalds
2020-11-17 19:25       ` Jakub Jelinek
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=20201116130726.GD3121392@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --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=richard.guenther@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).