From: Willy Tarreau <w@1wt.eu>
To: Daniel Palmer <daniel@thingy.jp>
Cc: linux@weissschuh.net, kees@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/9] nolibc: Add static-pie support
Date: Sun, 1 Feb 2026 22:49:09 +0100 [thread overview]
Message-ID: <aX_KVT8hLjPPV_zQ@1wt.eu> (raw)
In-Reply-To: <CAFr9PX=tY6ES4-gVj5P9SA3H+ww7eQ4OAphX=sj=dPPC2M00AA@mail.gmail.com>
On Mon, Feb 02, 2026 at 06:45:40AM +0900, Daniel Palmer wrote:
> Hi Willy,
>
> On Mon, 2 Feb 2026 at 03:14, Willy Tarreau <w@1wt.eu> wrote:
> > $ diff -u ret0*size
> > --- ret0-6.19-rc7.size 2026-02-01 19:04:33.918536545 +0100
> > +++ ret0-daniel.size 2026-02-01 19:04:40.914761767 +0100
> > @@ -16,4 +16,5 @@
> > 0000000000000011 W raise
> > 0000000000000012 W abort
> > 0000000000000023 W memmove
> > -0000000000000098 W _start_c
> > +0000000000000086 W __start_c
> > +000000000000015f W _start_c
> >
> > The delta is indeed 333 bytes.
> >
> > Is there anything we could detect at build time to detect that we want to
> > go the heavy way ? Maybe we should only condition that code to __PIE__ ?
> > There's nothing critical, it's really about having an open discussion on
> > this, because we're trying to keep the minimal binaries small, and here
> > we're just doubling the size of the smallest ones all the time.
> >
> > Thanks!
> > Willy
>
> Thank you for the feedback. I'll work out a way of hiding all of the
> new code unless it's needed.
> I think there might still be some increase in size from splitting
> _start_c() into two parts though.
Yes but that's expected. We can spend a few bytes here and there for the
good cause, it's just that here there's an opportunity to avoid most of
them when not needed.
Thanks,
Willy
prev parent reply other threads:[~2026-02-01 21:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 7:44 [RFC PATCH 0/9] nolibc: Add static-pie support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 1/9] elf: Add relocation types used by nolibc Daniel Palmer
2026-02-01 16:25 ` Thomas Weißschuh
2026-01-31 7:44 ` [RFC PATCH 2/9] tools/nolibc: crt: Split _start_c() into stack-only and normal part Daniel Palmer
2026-02-01 16:33 ` Thomas Weißschuh
2026-01-31 7:44 ` [RFC PATCH 3/9] tools/nolibc: Add basic ELF self-relocation support for static PIE Daniel Palmer
2026-02-01 16:42 ` Thomas Weißschuh
2026-02-01 21:54 ` Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 4/9] tools/nolibc: m68k: Add relocation support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 5/9] tools/nolibc: x86: Add relocation support for x86_64 Daniel Palmer
2026-02-01 17:56 ` Willy Tarreau
2026-01-31 7:44 ` [RFC PATCH 6/9] tools/nolibc: riscv: Add relocation support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 7/9] tools/nolibc: arm: " Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 8/9] selftests/nolibc: Add option for building with -static-pie Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 9/9] fs/binfmt_elf_fdpic: Reflect that PIE binaries also work in KConfig help Daniel Palmer
2026-02-01 16:27 ` Thomas Weißschuh
2026-02-01 18:14 ` [RFC PATCH 0/9] nolibc: Add static-pie support Willy Tarreau
2026-02-01 21:45 ` Daniel Palmer
2026-02-01 21:49 ` Willy Tarreau [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=aX_KVT8hLjPPV_zQ@1wt.eu \
--to=w@1wt.eu \
--cc=daniel@thingy.jp \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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