From: Daniel Palmer <daniel@0x0f.com>
To: geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org
Cc: linux-kernel@vger.kernel.org, Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH] m68k: Enable dead code elimination
Date: Wed, 16 Apr 2025 20:42:40 +0900 [thread overview]
Message-ID: <20250416114240.2929832-1-daniel@0x0f.com> (raw)
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>
---
arch/m68k/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
index eb5bb6d36899..11835eb59d94 100644
--- a/arch/m68k/Kconfig
+++ b/arch/m68k/Kconfig
@@ -32,6 +32,7 @@ config M68K
select HAVE_ASM_MODVERSIONS
select HAVE_DEBUG_BUGVERBOSE
select HAVE_EFFICIENT_UNALIGNED_ACCESS if !CPU_HAS_NO_UNALIGNED
+ select HAVE_LD_DEAD_CODE_DATA_ELIMINATION
select HAVE_MOD_ARCH_SPECIFIC
select HAVE_UID16
select MMU_GATHER_NO_RANGE if MMU
--
2.47.2
next reply other threads:[~2025-04-16 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 11:42 Daniel Palmer [this message]
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
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=20250416114240.2929832-1-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--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®