From: Jakub Jelinek <jakub@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Uros Bizjak <ubizjak@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sean Christopherson <seanjc@google.com>,
"Andrew Pinski (QUIC)" <quic_apinski@quicinc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] Kconfig: Explicitly disable asm goto w/ outputs on gcc-11 (and earlier)
Date: Thu, 15 Feb 2024 20:26:32 +0100 [thread overview]
Message-ID: <Zc5laJzgwSPtHCTe@tucnak> (raw)
In-Reply-To: <CAHk-=wjLFrbAVq6bxjGk+cAuafRgW8-6fxjsWzdxngM-fy_cew@mail.gmail.com>
On Thu, Feb 15, 2024 at 11:17:44AM -0800, Linus Torvalds wrote:
> but the manual addition of 'volatile' is unconditional.
That is just fine. The extra keyword is not wrong, it is just redundant
with fixed compilers, where it doesn't change anything in the behavior.
Jakub
next prev parent reply other threads:[~2024-02-15 19:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 22:06 [PATCH] Kconfig: Explicitly disable asm goto w/ outputs on gcc-11 (and earlier) Sean Christopherson
2024-02-09 17:03 ` Nick Desaulniers
2024-02-09 17:14 ` Andrew Pinski (QUIC)
2024-02-09 17:55 ` Linus Torvalds
2024-02-09 18:43 ` Sean Christopherson
2024-02-09 18:55 ` Nick Desaulniers
2024-02-09 19:01 ` Linus Torvalds
2024-02-09 19:20 ` Nick Desaulniers
2024-02-09 20:39 ` Linus Torvalds
2024-02-09 21:46 ` Sean Christopherson
2024-02-10 17:21 ` David Laight
2024-02-11 11:12 ` Uros Bizjak
2024-02-11 19:59 ` Linus Torvalds
2024-02-11 20:12 ` Jakub Jelinek
2024-02-13 0:15 ` Sean Christopherson
2024-02-14 17:20 ` Sean Christopherson
2024-02-14 18:43 ` Linus Torvalds
2024-02-15 0:11 ` Linus Torvalds
2024-02-15 8:39 ` Jakub Jelinek
2024-02-15 18:25 ` Linus Torvalds
2024-02-15 19:17 ` Linus Torvalds
2024-02-15 19:26 ` Jakub Jelinek [this message]
2024-02-09 18:56 ` Linus Torvalds
2024-02-09 19:26 ` Andrew Pinski (QUIC)
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=Zc5laJzgwSPtHCTe@tucnak \
--to=jakub@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=quic_apinski@quicinc.com \
--cc=seanjc@google.com \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
/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