From: Nathan Chancellor <nathan@kernel.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: llvm@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: Latest clang versions fail to compile CONFIG_X86_X32_ABI=y
Date: Mon, 14 Apr 2025 08:16:11 -0700 [thread overview]
Message-ID: <20250414151611.GA3404099@ax162> (raw)
In-Reply-To: <CANp29Y4FmGDXm3LWvW6D+JR8CWf=fvuiAseFb1h2HQSDjFKO2A@mail.gmail.com>
On Mon, Apr 14, 2025 at 04:11:15PM +0200, Aleksandr Nogikh wrote:
> Hi,
>
> I've been trying to build a Linux kernel using newer llvm toolchain
> versions (18, 19, 20), but it consistently fails with the following
> errors:
>
> ld.lld: error: arch/x86/entry/vdso/vgetrandom-x32.o:(.note.gnu.property+0x0):
> data is too short
> ld.lld: error: arch/x86/entry/vdso/vgetcpu-x32.o:(.note.gnu.property+0x0):
> data is too short
> ld.lld: error: arch/x86/entry/vdso/vclock_gettime-x32.o:(.note.gnu.property+0x0):
> data is too short
>
> The steps to reproduce:
> $ git checkout v6.15-rc2
> $ make defconfig
> $ ./scripts/config -e X86_X32_ABI
> $ make CC=clang LD=ld.lld -j48
>
> The versions used:
> $ clang --version
> Debian clang version 20.1.2
> (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97)
> $ ld.lld --version
> Debian LLD 20.1.2 (compatible with GNU linkers)
>
> Is this a known clang/Linux issue?
I am not aware of this but it is likely because as Thomas pointed out,
this invocation is only using clang/the integrated assembler and ld.lld,
not the entire LLVM toolchain, which is generally what we encourage
people to use unless there is a problem with doing so.
> There's a kernel commit that addresses a similar problem:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aaeed6ecc1253ce1463fa1aca0b70a4ccbc9fa75
>
> but the error is slightly different there and the added Kconfig
> condition apparently did not kick in.
What version of binutils is being used here ('objcopy --version')? I can
try and look into this and see if the Kconfig checks should be expanded
to include other tools/versions. I highly doubt anyone building with
LLVM would notice lack of x32 support, as I believe only Debian and
Gentoo have support for it and some x86 folks have tried to put it on
the chopping block before.
Cheers,
Nathan
next prev parent reply other threads:[~2025-04-14 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:11 Latest clang versions fail to compile CONFIG_X86_X32_ABI=y Aleksandr Nogikh
2025-04-14 14:29 ` Thomas Weißschuh
2025-04-14 15:16 ` Nathan Chancellor [this message]
2025-04-15 14:40 ` Aleksandr Nogikh
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=20250414151611.GA3404099@ax162 \
--to=nathan@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nogikh@google.com \
--cc=syzkaller@googlegroups.com \
/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