All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Borislav Petkov <bp@alien8.de>, kernel test robot <lkp@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Jinjie Ruan <ruanjinjie@huawei.com>
Subject: Re: [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token
Date: Wed, 2 Jul 2025 16:54:25 +0200	[thread overview]
Message-ID: <20250702145425.GS1613376@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aGU_IY70Jt4bcbf2@J2N7QTR9R3.cambridge.arm.com>

On Wed, Jul 02, 2025 at 03:16:01PM +0100, Mark Rutland wrote:
> On Wed, Jul 02, 2025 at 03:24:15PM +0200, Borislav Petkov wrote:
> > On Wed, Jul 02, 2025 at 02:16:15PM +0100, Mark Rutland wrote:
> > > Sounds like a plan.
> > 
> > As we figured out on IRC:
> > 
> > https://lore.kernel.org/all/20250616-loongarch-fix-warn-cond-llvm-ias-v1-1-6c6d90bb4466@kernel.org/
> > 
> > "clang's integrated assembler only supports concatenating strings with
> > '.ascii'. There was discussion of allowing '.string' / '.asciz' but it
> > was decided against [1] because it was undesirable to match the behavior
> > of released binutils at the time, where"
> > 
> > and this seems to fix it here:
> > 
> > ---
> > diff --git a/arch/s390/include/asm/bug.h b/arch/s390/include/asm/bug.h
> > index a185855ab158..46d9eb64bd18 100644
> > --- a/arch/s390/include/asm/bug.h
> > +++ b/arch/s390/include/asm/bug.h
> > @@ -9,7 +9,7 @@
> >  #else
> >  #define __BUGVERBOSE_LOCATION(file, line)			\
> >  		.pushsection .rodata.str, "aMS", @progbits, 1;	\
> > -	10002:	.string file;					\
> > +	10002:	.ascii file;					\
> >  		.popsection;					\
> >  								\
> >  		.long 10002b - .;				\
> > 
> 
> IIUC this also needs a trailing "\0" as per the link above, or this
> won't get a NUL-terminator (but will build just fine).

Yup, I ran into this before. Let me go fix that commit.

  reply	other threads:[~2025-07-02 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 21:56 [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token kernel test robot
2025-07-02 12:32 ` Borislav Petkov
2025-07-02 12:58   ` Mark Rutland
2025-07-02 13:09     ` Borislav Petkov
2025-07-02 13:16       ` Mark Rutland
2025-07-02 13:24         ` Borislav Petkov
2025-07-02 14:16           ` Mark Rutland
2025-07-02 14:54             ` Peter Zijlstra [this message]
2025-07-02 15:07               ` Peter Zijlstra
2025-07-02 15:41                 ` Heiko Carstens
2025-07-02 16:10                   ` Peter Zijlstra
2025-07-02 18:01                     ` Nathan Chancellor
2025-07-02 18:12                       ` Borislav Petkov
2025-07-02 18:29                         ` Borislav Petkov
2025-07-02 18:38                           ` Nathan Chancellor
2025-07-02 18:40                             ` Borislav Petkov

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=20250702145425.GS1613376@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mark.rutland@arm.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ruanjinjie@huawei.com \
    --cc=tglx@linutronix.de \
    --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 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.