public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Michal Marek <mmarek@suse.com>, linux-kbuild@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	linux-arch@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@linaro.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Alan Modra <amodra@gmail.com>
Subject: [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections
Date: Wed, 24 Aug 2016 22:29:18 +1000	[thread overview]
Message-ID: <1472041761-14414-1-git-send-email-npiggin@gmail.com> (raw)

Hi Michal,

I ended up deciding to do a v3, because I had several changes
accumulated, as described in patches.

I've also left off the powerpc arch patches -- they can be found
in previous posts, for reference.

I've again tested ARM and it seems to be building okay and without
performance regression with my configurations. I think it's going
to be a matter of some toolchain options for them to go through.
arm64, x86, powerpc, and arm for me all built fine with thin archives
and --gc-sections enabled, so I can't see there being a fundamental
issue that can't be solved. Worst case, the incremental link option
can remain for a time.

Thanks,
Nick

Nicholas Piggin (2):
  kbuild: allow archs to select link dead code/data elimination
  kbuild: add arch specific post-link Makefile

Stephen Rothwell (1):
  kbuild: allow architectures to use thin archives instead of ld -r

 Documentation/kbuild/makefiles.txt | 16 +++++++++
 Makefile                           | 19 ++++++++--
 arch/Kconfig                       | 26 ++++++++++++++
 include/asm-generic/vmlinux.lds.h  | 52 ++++++++++++++++------------
 include/linux/compiler.h           | 23 ++++++++++++
 include/linux/export.h             | 30 ++++++++--------
 include/linux/init.h               | 38 +++++++-------------
 init/Makefile                      |  2 ++
 scripts/Makefile.build             | 23 +++++++++---
 scripts/Makefile.modpost           | 14 +++++---
 scripts/link-vmlinux.sh            | 71 ++++++++++++++++++++++++++++++++------
 11 files changed, 228 insertions(+), 86 deletions(-)

-- 
2.8.1


             reply	other threads:[~2016-08-24 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 12:29 Nicholas Piggin [this message]
2016-08-24 12:29 ` [PATCH 1/3] kbuild: allow architectures to use thin archives instead of ld -r Nicholas Piggin
2016-08-24 12:29 ` [PATCH 2/3] kbuild: allow archs to select link dead code/data elimination Nicholas Piggin
2016-08-24 12:29 ` [PATCH 3/3] kbuild: add arch specific post-link Makefile Nicholas Piggin
2016-08-24 13:32   ` Nicholas Piggin
2016-08-24 13:06 ` [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections Arnd Bergmann
2016-08-24 15:13   ` Nicolas Pitre
2016-08-24 14:21 ` David Howells
2016-08-24 15:21   ` Nicolas Pitre
2016-08-25  2:56     ` Nicholas Piggin
2016-09-09  0:23 ` Nicolas Pitre
2016-09-09 10:59   ` Michal Marek
2016-09-10  4:05     ` Nicolas Pitre

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=1472041761-14414-1-git-send-email-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=amodra@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=nico@linaro.org \
    --cc=sam@ravnborg.org \
    --cc=segher@kernel.crashing.org \
    --cc=sfr@canb.auug.org.au \
    /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