From: Daniel Jacobowitz <drow@false.org>
To: Thiemo Seufer <ths@networkno.de>
Cc: binutils@sources.redhat.com
Subject: Re: RFA: Adjust MIPS hidden symbol handling
Date: Fri, 15 Apr 2005 02:35:00 -0000 [thread overview]
Message-ID: <20050415023525.GA32367@nevyn.them.org> (raw)
In-Reply-To: <20050413172116.GC32470@hattusa.textio>
On Wed, Apr 13, 2005 at 07:21:16PM +0200, Thiemo Seufer wrote:
> Daniel Jacobowitz wrote:
> [snip]
> > 2005-04-13 Daniel Jacobowitz <dan@codesourcery.com>
> >
> > * elfxx-mips.c (struct mips_got_entry): Update comment.
> > (struct mips_elf_link_hash_entry): Remove forced_local.
> > (mips_elf_link_hash_newfunc): Don't initialize forced_local.
> > (mips_elf_create_local_got_entry): Check h->root.forced_local
> > instead.
> > (mips_elf_make_got_per_bfd): Likewise.
> > (_bfd_mips_elf_hide_symbol): Likewise. Don't set forced_local.
>
> Ok.
Unfortunately, not.
I still think the patch is right in principle, and without it I get all
sorts of assertion failures - but with it, I don't get enough room
allocated for local GOT entries.
What I think is happening is that without the patch, several kinds of
hidden symbols are given unnecessary (and probably undesirable) global
GOT entries. With it, they're given local GOT entries - but something
else needs to be adjusted to account for it.
I'm going to keep looking into this :-( I'd _like_ to fix it for 2.16,
but 2.16 is running late already.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-15 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 17:56 Daniel Jacobowitz
2005-04-13 18:00 ` Thiemo Seufer
2005-04-15 2:35 ` Daniel Jacobowitz [this message]
2005-04-19 18:36 ` Daniel Jacobowitz
2005-04-19 18:51 ` Maciej W. Rozycki
2005-04-19 18:54 ` 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=20050415023525.GA32367@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=ths@networkno.de \
/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).