From: Thiemo Seufer <ths@networkno.de>
To: David Daney <ddaney@avtrex.com>, binutils@sourceware.org
Subject: Re: RFH/RFC: symbol index overflow in MIPS linker stubs...
Date: Wed, 07 Jun 2006 23:22:00 -0000 [thread overview]
Message-ID: <20060607204250.GF9732@networkno.de> (raw)
In-Reply-To: <20060607200930.GA19246@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Wed, Jun 07, 2006 at 09:03:30PM +0100, Thiemo Seufer wrote:
> > Daniel Jacobowitz wrote:
> > > On Wed, Jun 07, 2006 at 08:27:59PM +0100, Thiemo Seufer wrote:
> > > > I would favour a two instruction sequence, applications will continue to
> > > > grow. There might be some compatibility traps, but at a superficial
> > > > glance I haven't found an obvious blocker.
> > >
> > > If we can change the stub sequence without ABI problems, why waste an
> > > instruction? Support both.
> >
> > Will the stub section support varying entry sizes? I'm not sure.
>
> This is solveable, as a simple matter of programming, or ignorable,
> by padding the shorter entries with a trailing nop.
The first two entries are handled specially, this makes the second
option more likely. OTOH, saving an instruction when we have anyway
branches and memory access in between is probably not worth much.
Thiemo
next prev parent reply other threads:[~2006-06-07 20:45 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 [this message]
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
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=20060607204250.GF9732@networkno.de \
--to=ths@networkno.de \
--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).