From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Florian Weimer <fweimer@redhat.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-toolchains@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jason Baron <jbaron@akamai.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
dmalcolm@redhat.com
Subject: Re: static_branch/jump_label vs branch merging
Date: Sat, 10 Apr 2021 12:02:36 -0500 [thread overview]
Message-ID: <20210410170236.GJ26583@gate.crashing.org> (raw)
In-Reply-To: <CAKwvOdnBXyR6gPgQjaXbHF8Ozx9Kk=OKgPv8_P7=jvvsWRVHEg@mail.gmail.com>
On Fri, Apr 09, 2021 at 12:33:29PM -0700, Nick Desaulniers wrote:
> Since asm goto is implicitly volatile qualified, it sounds like
> removing the implicit volatile qualifier from asm goto might help?
> Then if there were side effects but you forgot to inform the compiler
> that there were via an explicit volatile qualifier, and it performed
> the suggested merge, oh well.
"asm goto" without outputs is always volatile, just like any other asm
without outputs (if it wasn't, the compiler would always delete every
asm without outputs!)
Segher
next prev parent reply other threads:[~2021-04-10 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 16:52 static_branch/jump_label vs branch merging Peter Zijlstra
2021-04-09 9:57 ` Ard Biesheuvel
2021-04-09 10:55 ` Florian Weimer
2021-04-09 11:16 ` Peter Zijlstra
2021-04-09 19:33 ` Nick Desaulniers
2021-04-09 20:11 ` Peter Zijlstra
2021-04-10 17:02 ` Segher Boessenkool [this message]
2021-04-09 11:12 ` Peter Zijlstra
2021-04-09 11:55 ` David Malcolm
2021-04-09 12:03 ` Peter Zijlstra
2021-04-09 13:01 ` Peter Zijlstra
2021-04-09 13:13 ` Peter Zijlstra
2021-04-09 13:48 ` David Malcolm
2021-04-09 18:40 ` Peter Zijlstra
2021-04-09 19:21 ` David Malcolm
2021-04-09 20:09 ` Peter Zijlstra
2021-04-09 21:07 ` David Malcolm
2021-04-09 21:39 ` Peter Zijlstra
2021-04-22 11:48 ` Peter Zijlstra
2021-04-22 17:08 ` Segher Boessenkool
2021-04-22 17:49 ` Peter Zijlstra
2021-04-22 18:31 ` Segher Boessenkool
2021-04-26 17:13 ` Peter Zijlstra
2021-04-10 12:44 ` David Laight
2021-04-09 13:03 ` Segher Boessenkool
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=20210410170236.GJ26583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=ardb@kernel.org \
--cc=dmalcolm@redhat.com \
--cc=fweimer@redhat.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 NNTP newsgroup(s).