public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel•org>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel•org>
Cc: Thomas Gleixner <tglx@linutronix•de>,
	kernel test robot <lkp@intel•com>,
	llvm@lists•linux.dev, oe-kbuild-all@lists•linux.dev,
	linux-kernel@vger•kernel.org, x86@kernel•org,
	Ingo Molnar <mingo@kernel•org>,
	"Peter Zijlstra (Intel)" <peterz@infradead•org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios•com>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [tip:core/rseq 25/39] include/linux/rseq_entry.h:132:3: error: invalid operand for instruction
Date: Tue, 25 Nov 2025 16:39:33 -0700	[thread overview]
Message-ID: <20251125233933.GA1102709@ax162> (raw)
In-Reply-To: <20251125231834.GA4012217@ax162>

On Tue, Nov 25, 2025 at 04:18:34PM -0700, Nathan Chancellor wrote:
> That avoids the error for me. I notice that this does not reproduce
> beyond clang-16 for me so I am going to bisect LLVM to see what fixes
> this error.

Oh, it is because of commit e2ffa15b9baa ("kbuild: Disable
CC_HAS_ASM_GOTO_OUTPUT on clang < 17"). Prior to that change, all
supported versions of clang would use the CONFIG_CC_HAS_ASM_GOTO_OUTPUT
blocks in arch/powerpc/include/asm/uaccess.h, whereas now clang-15 and
clang-16 will use the variants without asm goto with outputs.

Cheers,
Nathan


      reply	other threads:[~2025-11-25 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202511250134.i0Jm8d7I-lkp@intel.com>
2025-11-24 19:15 ` [tip:core/rseq 25/39] include/linux/rseq_entry.h:132:3: error: invalid operand for instruction Thomas Gleixner
2025-11-25  2:28   ` Philip Li
2025-11-25  7:38   ` Christophe Leroy (CS GROUP)
2025-11-25 23:18     ` Nathan Chancellor
2025-11-25 23:39       ` Nathan Chancellor [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=20251125233933.GA1102709@ax162 \
    --to=nathan@kernel$(echo .)org \
    --cc=chleroy@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=lkp@intel$(echo .)com \
    --cc=llvm@lists$(echo .)linux.dev \
    --cc=mathieu.desnoyers@efficios$(echo .)com \
    --cc=mingo@kernel$(echo .)org \
    --cc=oe-kbuild-all@lists$(echo .)linux.dev \
    --cc=peterz@infradead$(echo .)org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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