From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Thomas Gleixner <tglx@kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: kernel/futex/core.c:604:23: error: cannot jump from this asm goto statement to one of its possible targets
Date: Wed, 4 Feb 2026 09:22:21 +0100 [thread overview]
Message-ID: <20260204082221.GC3016024@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260203035603.GC52989@ax162>
On Mon, Feb 02, 2026 at 08:56:03PM -0700, Nathan Chancellor wrote:
> This appears to be the same error that necessitated e2ffa15b9baa ("kbuild:
> Disable CC_HAS_ASM_GOTO_OUTPUT on clang < 17") upstream but this is just
> regular 'asm goto', not 'asm goto' with outputs. I had noted during
> review that change might not be sufficient to avoid the error in all
> cases:
>
> https://lore.kernel.org/20250916184440.GA1245207@ax162/
>
> This is not the only recent instance of this error because cleanup
> macros are becoming quite popular so I think it is getting to the point
> where we will need to raise the minimum supported version of LLVM for
> building the kernel to 17.0.1 or newer to ensure that we have this
> fixed. LLVM 22.1.0 should be released in a month or so, so I can look at
> crafting a series for 7.1/7.2 that does this bump.
Works for me, more recent compiler more better and all that ;-)
prev parent reply other threads:[~2026-02-04 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 19:34 kernel/futex/core.c:604:23: error: cannot jump from this asm goto statement to one of its possible targets kernel test robot
2026-02-03 3:56 ` Nathan Chancellor
2026-02-04 8:22 ` Peter Zijlstra [this message]
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=20260204082221.GC3016024@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@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