public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard@codesourcery.com>
To: David Daney <ddaney@avtrex.com>
Cc: binutils@sourceware.org
Subject: Re: RFH/RFC: symbol index overflow in MIPS linker stubs...
Date: Thu, 08 Jun 2006 18:44:00 -0000	[thread overview]
Message-ID: <87y7w7pkcd.fsf@talisman.home> (raw)
In-Reply-To: <44886C39.2090202@avtrex.com> (David Daney's message of "Thu, 08 	Jun 2006 11:28:09 -0700")

David Daney <ddaney@avtrex.com> writes:
> Richard Sandiford wrote:
>> David Daney <ddaney@avtrex.com> writes:
>> 
>>>There are three ways to do this:
>>>
>>>1) Always use a 20 byte stub.  This allows for up to 2^31 - 1 dynamic 
>>>symbols.  You are concerned that this would break IRIX tools.
>> 
>> 
>> Well, "would"'s a bit a too strong.  It's only a vague "might".
>> It's o32 I'm particularly worried about: the o32 IRIX tools
>> are a bit weird.
>> 
>> That wouldn't be much of an argument if it wasn't fairly easy
>> to do #2 or #3, of course, but it does look fairly easy.
>> 
>
> My main concern is that in _bfd_mips_elf_adjust_dynamic_symbol I need to 
> know the size of the stub, but I am uncertain if we will know the number 
> of dynamic symbols at this point so that we can choose the proper stub size.

AIUI, _bfd_mips_elf_adjust_dynamic_symbol is called after
_bfd_mips_elf_always_size_sections (see bfd_elf_size_dynamic_sections)
so I think we're OK there.

Richard

      reply	other threads:[~2006-06-08 18:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 19:29 David Daney
2006-06-07 19:38 ` Thiemo Seufer
2006-06-07 19:45   ` David Daney
2006-06-07 20:05   ` Daniel Jacobowitz
2006-06-07 20:10     ` Thiemo Seufer
2006-06-07 20:39       ` Daniel Jacobowitz
2006-06-07 20:45         ` David Daney
2006-06-07 23:22         ` Thiemo Seufer
2006-06-08 18:21 ` Richard Sandiford
2006-06-08 18:50   ` Thiemo Seufer
2006-06-08 19:35   ` David Daney
2006-06-08 18:27     ` Richard Sandiford
2006-06-08 18:35       ` David Daney
2006-06-08 18:44         ` Richard Sandiford [this message]

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=87y7w7pkcd.fsf@talisman.home \
    --to=richard@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=ddaney@avtrex.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 read-only IMAP folder(s) and NNTP newsgroup(s).