mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Guo Ren <guoren@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	 Palmer Dabbelt <palmer@dabbelt.com>, Fangrui Song <i@maskray.me>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
		linux-csky@vger.kernel.org, loongarch@lists.linux.dev,
		linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org,
		linux-kernel@vger.kernel.org
Subject: Re: Ping: [PATCH 0/3] Drop explicit --hash-style= setting for new
Date: Sun, 30 Mar 2025 20:18:02 +0800	[thread overview]
Message-ID: <42dc2fc95fc9d56abd68ec620b29602eef9aa742.camel@xry111.site> (raw)
In-Reply-To: <CAJF2gTRXyMX+9C_aEDbxAsxWDD2rbnDWO775YDZ3EmrQ=QinfQ@mail.gmail.com>

On Mon, 2025-03-10 at 10:13 +0800, Guo Ren wrote:
> On Wed, Mar 5, 2025 at 9:27 PM Xi Ruoyao <xry111@xry111.site> wrote:
> > 
> > Ping.
> > 
> > On Mon, 2025-02-24 at 19:20 +0800, Xi Ruoyao wrote:
> > > For riscv, csky, and LoongArch, GNU hash had already become the de-
> > > facto
> > > standard when they borned, so there's no Glibc/Musl releases for them
> > > without GNU hash support, and the traditional SysV hash is just
> > > wasting
> > > space for them.
> > > 
> > > Remove those settings and follow the distro toolchain default, which
> > > is
> > > likely --hash-style=gnu.  In the past it could break vDSO self tests,
> > > but now the issue has been addressed by commit
> > > e0746bde6f82 ("selftests/vDSO: support DT_GNU_HASH").
> > > 
> > > Xi Ruoyao (3):
> > >   riscv: vDSO: Remove --hash-style=both
> The patch's comment is incorrect; when I removed --hash-style=both,
> the output still contained the HASH, and no space was saved.

The idea is following the distro toolchain default (which can be
configured building binutils).

If the distro toolchain default is gnu, we'll use gnu.

If the distro toolchain default is both, the distro is already wasting
space everywhere for (a) some bizarre applications depending on DT_HASH
for some bizzare reason; or (b) an oversight.

In the case of (a) the bizarre application may needs DT_HASH in vDSO as
well, and in the case of (b) it should be fixed for the entire distro,
not only vDSO, for example what we are doing for AOSC:
https://github.com/AOSC-Dev/aosc-os-abbs/pull/9531

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2025-03-30 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 11:20 Xi Ruoyao
2025-02-24 11:20 ` [PATCH 1/3] riscv: vDSO: Remove --hash-style=both Xi Ruoyao
2025-02-24 11:20 ` [PATCH 2/3] csky: " Xi Ruoyao
2025-02-24 11:20 ` [PATCH 3/3] LoongArch: vDSO: Remove --hash-style=sysv Xi Ruoyao
2025-03-30  9:55   ` Huacai Chen
2025-03-05 13:27 ` Ping: [PATCH 0/3] Drop explicit --hash-style= setting for new Xi Ruoyao
2025-03-10  2:13   ` Guo Ren
2025-03-30 12:18     ` Xi Ruoyao [this message]
2025-05-09 17:30 ` patchwork-bot+linux-riscv

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=42dc2fc95fc9d56abd68ec620b29602eef9aa742.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=chenhuacai@kernel.org \
    --cc=guoren@kernel.org \
    --cc=i@maskray.me \
    --cc=kernel@xen0n.name \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=yangtiezhu@loongson.cn \
    /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®