From: Nathan Chancellor <nathan@kernel.org>
To: Vishal Chourasia <vishalc@linux.ibm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>
Subject: Re: [PATCH] arch/powerpc: Remove .interp section in vmlinux
Date: Tue, 14 Oct 2025 17:21:54 -0700 [thread overview]
Message-ID: <20251015002154.GA2300901@ax162> (raw)
In-Reply-To: <aOypxKMzsLR5tAtv@linux.ibm.com>
Hi Vishal,
On Mon, Oct 13, 2025 at 12:57:00PM +0530, Vishal Chourasia wrote:
> On Mon, Oct 13, 2025 at 08:46:48AM +0200, Christophe Leroy wrote:
> > +CLANG ppl
> >
> > Hi,
> >
> > Le 13/10/2025 à 06:01, Vishal Chourasia a écrit :
> > > While debugging a ppc64le QEMU guest on an x86_64 host, I observed GDB crashes
> > > when attempting to attach to the remote target:
> > >
> > > (gdb) target remote :1234
> > >
> > > Investigation revealed that cross-compiling the Linux kernel for ppc64le on an
> > > x86_64 host using Clang produces a vmlinux binary containing an empty .interp
> > > section. This empty .interp section is responsible for the GDB crashes.
> >
> > Which version of CLANG is it ?
> (i) ❯ clang --version
> clang version 21.0.0git (https://github.com/llvm/llvm-project.git a80bccc6847be104948f46d313f03ac6b9ccb292)
>
> >
> > >
> > > This issue does not occur when:
> > > - Building for ppc64le target using GCC on x86_64 host
> > > - Building for ppc64le target using Clang on ppc64le host
> >
> > Is it the same CLANG version ?
> # clang --version
> clang version 22.0.0git (https://github.com/llvm/llvm-project.git 2f755c543ab357bd83235592fcee37fa391cdd9d)
>
> >
> > > - Building for ppc64le target using GCC on ppc64le host
> > >
> > > For details refer [1]
> > >
> > > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=33481
In this bug report, you mention using LLVM=1. Does the issue happen if
you use GNU ld (ld.bfd) via LD (i.e., LD=powerpc64le-linux-gnu-ld or
equivalent) over ld.lld from LLVM=1? This sounds more likely to be a
linker difference rather than a compiler difference.
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-15 0:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 10:49 [PATCH] arch/powerpc: Remove .interp section in vmlinux Christophe Leroy
2025-07-01 13:32 ` Segher Boessenkool
2025-10-13 4:01 ` Vishal Chourasia
2025-10-13 6:46 ` Christophe Leroy
2025-10-13 7:27 ` Vishal Chourasia
2025-10-15 0:21 ` Nathan Chancellor [this message]
2025-10-15 3:37 ` Vishal Chourasia
2025-10-15 18:27 ` Nathan Chancellor
2025-10-16 6:06 ` Vishal Chourasia
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=20251015002154.GA2300901@ax162 \
--to=nathan@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=vishalc@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).