From: Peter Zijlstra <peterz@infradead.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Jean Delvare <jdelvare@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
ardb@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: Build breakage caused by the use of UDB
Date: Thu, 18 Dec 2025 09:54:47 +0100 [thread overview]
Message-ID: <20251218085447.GJ3707891@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFULd4Y4oBq67Vr3F2Zye1FazjZtRU+7zeGagAz74LRNGVkcEA@mail.gmail.com>
On Wed, Dec 17, 2025 at 03:39:07PM +0100, Uros Bizjak wrote:
> > > What's worse, it only sometimes does this:
> > >
> > > $ grep ".byte[ ]*0x0f" defconfig-build/drivers/net/wireless/realtek/rtlwifi/base.s
> > > 1: .byte0x0f,0x0b ;
> > > 1: .byte 0x0f,0x0b ;
> > >
> > > W.T.F. and all that.
> How about the attached patch that ensures that separator survives
> macro expansion?
Right, I think I tried that, it doesn't like things like retpoline.S
> diff --git a/arch/x86/include/asm/asm.h b/arch/x86/include/asm/asm.h
> index 0e8c611bc9e2..76d2eb96dd49 100644
> --- a/arch/x86/include/asm/asm.h
> +++ b/arch/x86/include/asm/asm.h
> @@ -17,7 +17,7 @@
> # define __ASM_REGPFX %%
> #endif
>
> -#define _ASM_BYTES(x, ...) __ASM_FORM(.byte x,##__VA_ARGS__ ;)
> +#define _ASM_BYTES(x, ...) __ASM_FORM(.byte\t x,##__VA_ARGS__)
>
> #ifndef __x86_64__
> /* 32 bit */
$ make O=defconfig-build/ CC=gcc-8 arch/x86/lib/retpoline.o
make[1]: Entering directory '/mnt/nvme/linux-2.6/defconfig-build'
GEN Makefile
CALL ../scripts/checksyscalls.sh
DESCEND objtool
INSTALL libsubcmd_headers
AS arch/x86/lib/retpoline.o
../arch/x86/include/asm/GEN-for-each-reg.h: Assembler messages:
../arch/x86/include/asm/GEN-for-each-reg.h:140: Error: bad expression
../arch/x86/include/asm/GEN-for-each-reg.h:6: Info: macro invoked from here
../arch/x86/include/asm/GEN-for-each-reg.h:140: Error: junk at end of line, first unrecognized character is `t'
Which is why I ended up splitting the definition :/
next prev parent reply other threads:[~2025-12-18 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:44 Build breakage caused by the use of UDB Jean Delvare
2025-12-17 12:35 ` Peter Zijlstra
2025-12-17 12:47 ` Peter Zijlstra
2025-12-17 13:02 ` Peter Zijlstra
2025-12-17 13:34 ` Peter Zijlstra
2025-12-17 14:39 ` Uros Bizjak
2025-12-18 8:54 ` Peter Zijlstra [this message]
2025-12-18 10:26 ` Uros Bizjak
2025-12-18 10:38 ` Peter Zijlstra
2025-12-18 10:46 ` Peter Zijlstra
2025-12-18 11:03 ` [tip: x86/urgent] x86/bug: Fix old GCC compile fails tip-bot2 for Peter Zijlstra
2025-12-18 12:38 ` Build breakage caused by the use of UDB Brian Gerst
2025-12-17 13:10 ` Jean Delvare
2025-12-17 13:22 ` Peter Zijlstra
2025-12-17 22:07 ` Jean Delvare
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=20251218085447.GJ3707891@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ardb@kernel.org \
--cc=jdelvare@suse.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=x86@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