All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Richard Biener <richard.guenther@gmail.com>,
	"Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"amonakov@ispras.ru" <amonakov@ispras.ru>,
	"ubizjak@gmail.com" <ubizjak@gmail.com>,
	"luto@kernel.org" <luto@kernel.org>,
	linux-toolchains@vger.kernel.org, Will Deacon <will@kernel.org>
Subject: Re: Re: typeof and operands in named address spaces
Date: Tue, 17 Nov 2020 11:13:52 -0800	[thread overview]
Message-ID: <CAHk-=wh_kn11vXfi2Ns8E4F0GgmUprQtD-=RnU6Eg+N7coY5gw@mail.gmail.com> (raw)
In-Reply-To: <20201116111056.GA3121378@hirez.programming.kicks-ass.net>

On Mon, Nov 16, 2020 at 3:11 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> XXX: I've only verified the below actually compiles, I've not verified
>      the generated code is actually 'correct'.

Well, it was mainly the arm64 code generation for load-acquire and
store-release that wanted this - so it's really the generated code
that matters.

Will, can you check?

Because:

> +#define __unqual_typeof(type)  typeof( (typeof(type))type )

that's certainly a much nicer version than the existing pre-processor
expansion from hell.

             Linus

  parent reply	other threads:[~2020-11-17 19:14 UTC|newest]

Thread overview: 20+ 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 [this message]
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
2020-11-17 21:28         ` [PATCH] casts should drop qualifiers Luc Van Oostenryck
2020-11-17 23:22           ` Linus Torvalds
2020-11-17 23:50             ` Luc Van Oostenryck
2020-11-18 18:31             ` Linus Torvalds
2020-11-18 19:17               ` Luc Van Oostenryck
2020-11-18 19:51                 ` Linus Torvalds
2020-11-18 21:30                   ` Luc Van Oostenryck
2020-11-19  0:58                     ` Linus Torvalds
2020-11-19  8:11                       ` Luc Van Oostenryck

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='CAHk-=wh_kn11vXfi2Ns8E4F0GgmUprQtD-=RnU6Eg+N7coY5gw@mail.gmail.com' \
    --to=torvalds@linux-foundation.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=peterz@infradead.org \
    --cc=richard.guenther@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.