From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-arch@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>,
David Howells <dhowells@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>,
Lennert Buytenhek <kernel@wantstofly.org>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Andi Kleen <andi@firstfloor.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
Tim Bird <tim.bird@am.sony.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Dave Miller <davem@davemloft.net>
Subject: Re: [PATCH 14/23] make section names compatible with -ffunction-sections -fdata-sections: parisc
Date: Wed, 02 Jul 2008 15:57:42 +0100 [thread overview]
Message-ID: <1215010662.10393.459.camel@pmac.infradead.org> (raw)
In-Reply-To: <20080702145514.GC4196@cs181140183.pp.htv.fi>
On Wed, 2008-07-02 at 17:55 +0300, Adrian Bunk wrote:
> On Wed, Jul 02, 2008 at 09:41:47AM +0100, David Woodhouse wrote:
> > On Wed, 2008-07-02 at 02:00 +0200, Denys Vlasenko wrote:
> > > On Wednesday 02 July 2008 01:41, James Bottomley wrote:
> > > > On Wed, 2008-07-02 at 02:39 +0200, Denys Vlasenko wrote:
> > > > > The purpose of this patch is to make kernel buildable
> > > > > with "gcc -ffunction-sections -fdata-sections".
> > > > > This patch fixes parisc architecture.
> > > > >
> > > > > Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
> > > >
> > > > Um ... if you look at the Makefile you'll see we already build parisc
> > > > with -ffunction-sections; we have to: our relative jumps are too small
> > > > to guarantee finding the stubs in large files.
> > > >
> > > > Since our text is -ffunction-sections compatible already, I question the
> > > > need for transformations like this:
> >
> > We've been building FR-V kernels with --gc-sections for a long time,
> > too.
> >...
>
> Is there any specific reason why it's not done in the upstream kernel?
Isn't it? I thought it was.
Or maybe we were only doing that before we added MMU support. I remember
the exception tables complicate matters a little.
--
dwmw2
next prev parent reply other threads:[~2008-07-02 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 0:39 [PATCH 14/23] make section names compatible with -ffunction-sections -fdata-sections: parisc Denys Vlasenko
2008-07-01 23:41 ` James Bottomley
2008-07-02 0:00 ` Denys Vlasenko
2008-07-02 1:23 ` James Bottomley
2008-07-02 8:41 ` David Woodhouse
2008-07-02 14:55 ` Adrian Bunk
2008-07-02 14:57 ` David Woodhouse [this message]
2008-07-02 15:06 ` Adrian Bunk
2008-07-06 15:46 ` Denys Vlasenko
2008-07-06 16:19 ` James Bottomley
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=1215010662.10393.459.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=kernel@wantstofly.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.com \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
/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).