All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: dhowells@redhat.com, Michal Marek <mmarek@suse.com>,
	linux-kbuild@vger.kernel.org, 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: Re: [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections
Date: Wed, 24 Aug 2016 15:21:21 +0100	[thread overview]
Message-ID: <12110.1472048481@warthog.procyon.org.uk> (raw)
In-Reply-To: <1472041761-14414-1-git-send-email-npiggin@gmail.com>

Out of interest, does using LTO also fix the problem?

David

  parent reply	other threads:[~2016-08-24 14:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 12:29 [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections Nicholas Piggin
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 [this message]
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=12110.1472048481@warthog.procyon.org.uk \
    --to=dhowells@redhat.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=npiggin@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.