From: Nathan Chancellor <nathan@kernel.org>
To: linaro-toolchain@lists.linaro.org
Cc: llvm@lists.linux.dev
Subject: Re: [Linaro-TCWG-CI] v6.17.3-130-g86f364ee5842: Failure on aarch64
Date: Tue, 28 Oct 2025 15:32:21 -0700 [thread overview]
Message-ID: <20251028223221.GA1306180@ax162> (raw)
In-Reply-To: <481166937.2108.1761498077256@jenkins.jenkins>
On Sun, Oct 26, 2025 at 05:01:16PM +0000, ci_notify@linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_kernel/llvm-master-aarch64-stable-allnoconfig, after:
> | commit v6.17.3-130-g86f364ee5842
> | Author: Masahiro Yamada <masahiroy@kernel.org>
> | Date: Thu Sep 18 10:05:46 2025 +0200
> |
> | kbuild: always create intermediate vmlinux.unstripped
> |
> | [ Upstream commit 0ce5139fd96e9d415d3faaef1c575e238f9bbd67 ]
> |
> | Generate the intermediate vmlinux.unstripped regardless of
> | ... 14 lines of the commit log omitted.
This is reproducible for me locally with:
$ make -skj"$(nproc)" ARCH=arm64 CC=clang CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=clang LD=ld.lld clean allnoconfig all
aarch64-linux-gnu-objcopy: vmlinux: file format not recognized
...
This does not occur with llvm-objcopy via LLVM=1 nor does it happen with
an all GNU setup. This feels like a bug in GNU objcopy though, as this
is reproducible with:
$ aarch64-linux-gnu-objcopy --set-section-flags .modinfo=noload vmlinux.unstripped vmlinux.objcopy
$ file vmlinux.unstripped vmlinux.objcopy
vmlinux.unstripped: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped
vmlinux.objcopy: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped
$ aarch64-linux-gnu-objcopy --remove-section=.modinfo -w --strip-unneeded-symbol='__mod_device_table__*' vmlinux.objcopy
aarch64-linux-gnu-objcopy: vmlinux.objcopy: file format not recognized
$ aarch64-linux-gnu-objcopy --version | head -1
GNU objcopy (GNU Binutils) 2.45.50.20251028
Cheers,
Nathan
prev parent reply other threads:[~2025-10-28 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 17:01 [Linaro-TCWG-CI] v6.17.3-130-g86f364ee5842: Failure on aarch64 ci_notify
2025-10-28 22:32 ` 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=20251028223221.GA1306180@ax162 \
--to=nathan@kernel.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=llvm@lists.linux.dev \
/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