mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: 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 13:58:50 +0100	[thread overview]
Message-ID: <aGUtCveV8Ev17_FS@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20250702123240.GDaGUm6Le4KLL7o_91@fat_crate.local>

Hi Boris,

[ adding Linux and Jinjie, since this is almost certainly due to the
  irqentry split ]

On Wed, Jul 02, 2025 at 02:32:40PM +0200, Borislav Petkov wrote:
> On Wed, Jul 02, 2025 at 05:56:06AM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> > head:   104f02a7798f7e8aba25545f9d485035532260b2
> > commit: 104f02a7798f7e8aba25545f9d485035532260b2 [19/19] Merge core/entry into tip/master
> > config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250702/202507020528.N0LtekXt-lkp@intel.com/config)
> > compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250702/202507020528.N0LtekXt-lkp@intel.com/reproduce)
> 
> I'm trying to follow your reproducer and installed binutils-s390x-linux-gnu.
> 
> However: 
> 
> make CC=clang HOSTCC=clang W=1 ARCH=s390 arch/s390/ 
>   SYNC    include/config/auto.conf.cmd
>   CALL    scripts/checksyscalls.sh
>   VDSO    arch/s390/kernel/vdso64/vdso64.so.dbg
> ld: unrecognised emulation mode: elf64_s390
> Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 elf_iamcu i386pep i386pe
> make[2]: *** [arch/s390/kernel/vdso64/Makefile:53: arch/s390/kernel/vdso64/vdso64.so.dbg] Error 1
> make[1]: *** [arch/s390/Makefile:150: vdso_prepare] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> 
> My linker can't do s390. So I need something else which your system has.

IIUC you can build with `LLVM=1` rather than `CC=clang` to force the use of
LLD (which should support s390 even if you don't have a GNU LD that does).

I have script to use the kernel.org GCC/LLVM builds from:

  https://www.kernel.org/pub/tools/crosstool/
  https://cdn.kernel.org/pub/tools/llvm/

... and I can reproduce this with:

  [mark@lakrids:~/src/linux]% git clean -qfdx
  [mark@lakrids:~/src/linux]% usekorg-llvm 18.1.6 make LLVM=1 ARCH=s390 -s allmodconfig
  [mark@lakrids:~/src/linux]% usekorg-llvm 18.1.6 make LLVM=1 ARCH=s390 -s  

... where that last step blows up with:

| init/main.c:972:6: error: unexpected token
|   972 |         if (WARN(!irqs_disabled(),
|       |             ^

... plus a whole bucnh of other gunk.

I'll take a look, and hopefully Linus and Jinie can too.

Mark.

  reply	other threads:[~2025-07-02 12:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 21:56 kernel test robot
2025-07-02 12:32 ` Borislav Petkov
2025-07-02 12:58   ` Mark Rutland [this message]
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
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=aGUtCveV8Ev17_FS@J2N7QTR9R3.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®