From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Subject: Re: binutils 2.17 branch
Date: Fri, 17 Mar 2006 15:16:00 -0000 [thread overview]
Message-ID: <20060317150703.GB11242@nevyn.them.org> (raw)
In-Reply-To: <20060317051704.GE6777@bubble.grove.modra.org>
On Fri, Mar 17, 2006 at 03:47:04PM +1030, Alan Modra wrote:
> Seriously, it's still somewhat of a hack. The fact that we throw away
> syms added for an unneeded lib means I'm relying on nothing
> (eg. backend add_symbol_hook) keeping pointers into the symbol hash
> table apart from the ones I already handle (undefs, sym_hashes).
Yeah, I noticed that. I see why you did it this way, though, and I
think it will work better now than before - but I'd like it to have
a bit of testing before it goes into a release; Debian folks have
been complaining about bad --as-needed behavior since they discovered
it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-17 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 3:04 Daniel Jacobowitz
2006-03-17 6:43 ` Alan Modra
2006-03-17 15:16 ` Daniel Jacobowitz [this message]
2006-03-17 15:46 ` Dmitry V. Levin
2006-04-08 19:14 ` Martin Michlmayr
2006-04-08 22:50 ` Dmitry V. Levin
2006-04-08 21:23 ` Martin Michlmayr
2006-04-14 21:42 ` Daniel Jacobowitz
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=20060317150703.GB11242@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).