From: Richard Sandiford <rdsandiford@googlemail.com>
To: binutils@sourceware.org
Cc: gcc@gcc.gnu.org, linux-mips@linux-mips.org
Subject: Re: RFC: Adding non-PIC executable support to MIPS
Date: Tue, 01 Jul 2008 21:43:30 +0100 [thread overview]
Message-ID: <87zlp149ot.fsf@firetop.home> (raw)
In-Reply-To: <20080701202236.GA1534@caradoc.them.org> (Daniel Jacobowitz's message of "Tue\, 1 Jul 2008 16\:22\:37 -0400")
Daniel Jacobowitz <dan@debian.org> writes:
> We've shipped our version. Richard's version has presumably also
> shipped.
Right.
> We did negotiate the ABI changes with MTI; this is not quite
> as good as doing it in full view, but it was the best we could manage
> and MTI is as close to a central authority for the MIPS psABI as
> exists today.
>
> Richard, what are your thoughts on reconciling the differences? You
> can surely guess that I want to avoid changing our ABI now, even for
> relatively significant technical reasons - I'm all ears if there's a
> major reason, but in the comparisons I do not see one.
I suppose I still support the trade-off between the 5-insn MIPS I stubs
(with extra-long variation for large PLT indices) and the absolute
.got.plt address I used. And I still think it's shame we're treating
STO_MIPS_PLT and STO_MIPS16 as separate; we then only have 1 bit of
st_other unclaimed.
However, IMO, your argument about MTI being the central authority
is a killer one. The purpose of the GNU tools should be to follow
appropriate standards where applicable (and extend them where it
seems wise). So from that point of view, I agree that the GNU tools
should follow the ABI that Nigel and MTI set down. Consider my
patch withdrawn.
TBH, the close relationship between CodeSourcery and MTI
make it difficult for a non-Sourcerer and non-MTI employee
to continue to be a MIPS maintainer. I won't be in-the-know
about this sort of thing.
I've been thinking about that a lot recently, since I heard about
your implementation. I kind-of guessed it had been agreed with MTI
beforehand (although I hadn't realised MTI themselves had written
the specification). Having thought it over, I think it would be best
if I stand down as a MIPS maintainer and if someone with the appropriate
commercial connections is appointed instead. I'd recommend any
combination of yourself, Adam Nemet and David Daney (subject to
said people being willing, of course).
Richard
next prev parent reply other threads:[~2008-07-01 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 17:58 RFC: Adding non-PIC executable support to MIPS Richard Sandiford
2008-06-30 20:59 ` David VomLehn
2008-06-30 21:19 ` Daniel Jacobowitz
2008-06-30 21:28 ` David VomLehn
2008-07-01 20:22 ` Daniel Jacobowitz
2008-07-01 20:43 ` Richard Sandiford [this message]
2008-07-01 22:02 ` Richard Sandiford
2008-07-02 7:00 ` Adam Nemet
2008-07-02 10:13 ` Thiemo Seufer
2008-07-02 12:08 ` Daniel Jacobowitz
2008-07-02 19:55 ` Richard Sandiford
2008-07-02 20:29 ` Daniel Jacobowitz
2008-07-24 16:16 ` Daniel Jacobowitz
2008-07-24 20:17 ` Daniel Jacobowitz
2008-07-24 20:24 ` Richard Sandiford
2008-07-24 20:56 ` Daniel Jacobowitz
2008-07-27 9:10 ` Richard Sandiford
2008-07-27 21:36 ` Mark Mitchell
2008-07-28 19:43 ` 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=87zlp149ot.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@linux-mips.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