All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vishal Chourasia <vishalc@linux.ibm.com>
To: Nathan Chancellor <nathan@kernel.org>
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: Wed, 15 Oct 2025 09:07:54 +0530	[thread overview]
Message-ID: <aO8XEhMdT19UOPlp@linux.ibm.com> (raw)
In-Reply-To: <20251015002154.GA2300901@ax162>

Hello Nathan,

On Tue, Oct 14, 2025 at 05:21:54PM -0700, Nathan Chancellor wrote:
> 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.

Thank you for the insight.

Yes, when using powerpc64le-linux-gnu-ld linker .interp section is not
emitted.

Command:
$ make LLVM=1 ARCH=powerpc LD=powerpc64le-linux-gnu-ld -j 8 zImage
$ llvm-readelf -p .comment vmlinux

String dump of section '.comment':
[     0] clang version 22.0.0git (https://github.com/llvm/llvm-project.git 7314565281ec28b745502c3f429fd431e16673eb)

$ llvm-readelf -p .interp vmlinux                                                                                    
llvm-readelf: warning: 'vmlinux': could not find section '.interp'


vishalc

  reply	other threads:[~2025-10-15  3:38 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
2025-10-15  3:37         ` Vishal Chourasia [this message]
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=aO8XEhMdT19UOPlp@linux.ibm.com \
    --to=vishalc@linux.ibm.com \
    --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=nathan@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.