From: Josh Triplett <josh@joshtriplett.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Status of function-sections work?
Date: Tue, 7 Jun 2011 01:43:49 -0700 [thread overview]
Message-ID: <20110607084349.GC4599@leaf> (raw)
In-Reply-To: <201106071011.15114.vda.linux@googlemail.com>
On Tue, Jun 07, 2011 at 10:11:15AM +0200, Denys Vlasenko wrote:
> On Monday 06 June 2011 03:15, Josh Triplett wrote:
> > Hello,
> >
> > I found your work in 2010 on using function-sections and data-sections
> > to eliminate unused code in the kernel. I'd like to make use of this
> > work to try to build an extremely space-constrained kernel.
> >
> > It looks like a few of your patches made it into the kernel, but most of
> > the linker script changes don't seem to have made it in. I wanted to
> > find out the status of this work. Do you still have this working? Do
> > you have versions of your patches for current Linux?
>
> parisc uses ^ in some identifiers. Therefore we need something like
> [A-Za-z0-9_$^]* in linker script. This wasn't working with GNU ld -
> ^ is not a valid char for pattern. Use of more general [!.]*
> was also impossible - ! is not a valid char too.
>
> Therefore I asked binutils people to fix this (they agreed) and
> decided to wait for a fixed binutils to be released.
Makes sense. Thanks for the explanation and status.
Do you know if the fix has gone into binutils, either in a release or
the latest snapshot from version control? If not, does a patch exist?
- Josh Triplett
next prev parent reply other threads:[~2011-06-07 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110606011531.GA1887@leaf>
2011-06-07 8:11 ` Status of function-sections work? Denys Vlasenko
2011-06-07 8:43 ` Josh Triplett [this message]
2011-06-07 15:06 ` Denys Vlasenko
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=20110607084349.GC4599@leaf \
--to=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.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 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.