From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Enable dead code elimination
Date: Sun, 6 Jul 2025 12:43:50 +0200 [thread overview]
Message-ID: <CAMuHMdVEO+o0Py3ioC6ohbJooQdMhD9AXTHD1j1y+C_1TqSAAg@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdV6efvaJuqVjnayyCs2KAbJmi52n0afLS=jh=nKN0y9Ng@mail.gmail.com>
On Sun, 6 Jul 2025 at 11:14, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Wed, 16 Apr 2025 at 13:42, Daniel Palmer <daniel@0x0f.com> wrote:
> > Allow the experimental dead code elimination config to be enabled.
> >
> > For my 68000 nommu config this frees up a few hundred K of memory
> > so seems worth while.
> >
> > Boot and build tested on nommu and mmu enabled configs.
> >
> > Before:
> > Memory: 5388K/8192K available (1986K kernel code, 114K rwdata,
> > 244K rodata, 92K init, 41K bss, 2624K reserved, 0K cma-reserved)
> >
> > After
> > Memory: 5684K/8192K available (1714K kernel code, 112K rwdata,
> > 228K rodata, 92K init, 37K bss, 2328K reserved, 0K cma-reserved)
> >
> > Signed-off-by: Daniel Palmer <daniel@0x0f.com>
>
> Thanks for your patch!
>
> Note that enabling this requires enabling CONFIG_EXPERT first, which is
> currently enabled in the Coldfire defconfigs, but not in the Classic
> defconfigs. For atari_defconfig, I see a size reduction of ca. 150 KiB
> (gcc 13.3.0).
Let's share the actual figures I had saved before:
$ bloat-o-meter vmlinux-v6.16-rc2+EXPERT{,+LD_DEAD_CODE_DATA_ELIMINATION}
add/remove: 0/2125 grow/shrink: 10275/32 up/down: 52254/-205419 (-153165)
[...]
Total: Before=5277826, After=5124661, chg -2.90%
dmesg:
-Memory: 265412K/276480K available (4345K kernel code, 486K
rwdata, 1240K rodata, 164K init, 143K bss, 10440K reserved, 0K
cma-reserved)
+Memory: 265616K/276480K available (4205K kernel code, 484K
rwdata, 1180K rodata, 160K init, 143K bss, 10236K reserved, 0K
cma-reserved)
gcc version 13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2025-07-06 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 11:42 Daniel Palmer
2025-04-27 23:37 ` Greg Ungerer
2025-04-29 0:04 ` Daniel Palmer
2025-04-29 2:18 ` Greg Ungerer
2025-06-08 8:32 ` Finn Thain
2025-06-08 9:22 ` Finn Thain
2025-06-08 9:36 ` Geert Uytterhoeven
2025-06-11 22:41 ` Daniel Palmer
2025-06-16 4:48 ` Finn Thain
2025-07-06 9:14 ` Geert Uytterhoeven
2025-07-06 10:43 ` Geert Uytterhoeven [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=CAMuHMdVEO+o0Py3ioC6ohbJooQdMhD9AXTHD1j1y+C_1TqSAAg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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 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®