From: Nicholas Piggin <npiggin@gmail.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 0/6] MIPS: Use thin archives & dead code elimination
Date: Fri, 21 Oct 2016 11:51:47 +1100 [thread overview]
Message-ID: <20161021115147.0f6eea51@roar.ozlabs.ibm.com> (raw)
Message-ID: <20161021005147.aRfdCTIMbXIiNKb-GSNXG7ubY3j6pGFBmifyv_RK_OM@z> (raw)
In-Reply-To: <20161020202705.3783-1-paul.burton@imgtec.com>
Hey Paul,
On Thu, 20 Oct 2016 21:26:59 +0100
Paul Burton <paul.burton@imgtec.com> wrote:
> This series fixes a few issues with CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
> and then enables it, along with CONFIG_THIN_ARCHIVES, for MIPS. This
> leads to a typical generic kernel build becoming ~5% smaller:
>
> add/remove: 0/3028 grow/shrink: 1/14 up/down: 18/-457362 (-457344)
> ...
> Total: Before=9001030, After=8543686, chg -5.08%
>
> Applies atop v4.9-rc1.
Very nice, and thanks for the kbuild fixes, I think they all look sane.
Let's try to get those kbuild fixes in through the kbuild tree first
(which has some other fixes required for 4.9). I can take them and send
them to kbuild maintainer if you like.
On powerpc we'll likely provide an option to select these manually for
4.9 because there has been the odd toolchain issue come up, so that's
something to consider.
For your linker script, you may consider putting the function sections
into the same input as other text. TEXT_TEXT does not include .text.*,
so mips's .text.* below it will catch those.
You may just open-code your TEXT_TEXT, and have:
*(.text.hot .text .text.fixup .text.unlikely .text.[0-9a-zA-Z_]*)
or similar.
Thanks,
Nick
next prev parent reply other threads:[~2016-10-21 0:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:26 [PATCH 0/6] MIPS: Use thin archives & dead code elimination Paul Burton
2016-10-20 20:26 ` Paul Burton
2016-10-20 20:27 ` [PATCH 1/6] kbuild: Keep device tree tables though " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-21 9:33 ` Sergei Shtylyov
2016-10-20 20:27 ` [PATCH 2/6] kbuild: Keep .init.setup section through " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 3/6] kbuild: Keep PCI fixups " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 4/6] kbuild: Keep earlycon table " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 5/6] MIPS: Ensure bss section ends on a long-aligned address Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-11-04 8:46 ` Marcin Nowakowski
2016-11-04 8:46 ` Marcin Nowakowski
2016-10-20 20:27 ` [PATCH 6/6] MIPS: Use thin archives & dead code elimination Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-21 0:51 ` Nicholas Piggin [this message]
2016-10-21 0:51 ` [PATCH 0/6] " Nicholas Piggin
2016-10-21 7:45 ` Paul Burton
2016-10-21 7:45 ` Paul Burton
2016-10-21 8:47 ` Nicholas Piggin
2016-10-21 8:47 ` Nicholas Piggin
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=20161021115147.0f6eea51@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).