From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-toolchains@vger.kernel.org
Subject: Re: objtool warning, branch, patch, and .config (GCC bug)
Date: Thu, 26 May 2022 10:08:49 +0200 [thread overview]
Message-ID: <20220526080849.GF6479@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220526080313.GM2578@worktop.programming.kicks-ass.net>
On Thu, May 26, 2022 at 10:03:13AM +0200, Peter Zijlstra wrote:
> Which is just bloody weird/broken if you ask me. What's worse, GCC-10
> does the same. Only when I use GCC-11 do I get sensible code again:
Just to clarify, I can reproduce using:
gcc-9 (Debian 9.4.0-5) 9.4.0
gcc-10 (Debian 10.3.0-15) 10.3.0
The good compiler is:
gcc-11 (Debian 11.3.0-1) 11.3.0
next prev parent reply other threads:[~2022-05-26 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 17:33 objtool warning, branch, patch, and .config Paul E. McKenney
2022-05-25 17:34 ` Paul E. McKenney
2022-05-26 8:03 ` objtool warning, branch, patch, and .config (GCC bug) Peter Zijlstra
2022-05-26 8:08 ` Peter Zijlstra [this message]
2022-05-26 9:02 ` Jakub Jelinek
2022-05-26 9:41 ` Peter Zijlstra
2022-05-26 11:32 ` Jakub Jelinek
2022-05-26 11:54 ` Peter Zijlstra
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=20220526080849.GF6479@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=paulmck@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.