public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: binutils@sources.redhat.com
Subject: Re: [PATCH] Fix MIPS ELF64 relocation howtos
Date: Mon, 27 Aug 2001 12:41:00 -0000	[thread overview]
Message-ID: <20010827214105.E4669@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <20010827120012.A10036@lucon.org>

H . J . Lu wrote:
[snip]
> > This means to use the specification as a guide as long as it's
> > reasonable for Linux. That's my intention, too. 
> 
> Good. While we are on it, here are things I'd like to see in the new
> `traditional 64bit MIPS ELF ABI':
> 
> 1. Make gp callee-saved.

Ok. We should also use the rest of the NewABI calling conventions.

> 2. Use RELA relocation if all possible.

My private patch does so already, and since the ABI draft claims some
essential relocations to be unsupported for REL, this should be used
for all MIPS ELF64 variants. It's the only sane way AFAICS.

> 3. Use relocations in the SGI 64bit ABI when make senses to us.

Ok. I made some steps towards this in my private patch for the
_HIGHER and _HIGHEST relocations.

> 4. Drop support for the MIPS/SGI quickstart.

Since there is no support for quickstart in binutils: already done. :-)

> 5. Add support for the glibc prelink.

This will be an issue when we can do PIC.

> #1 is a gcc only issue.

No, we need to handle .cpsetup, .cpreturn and possibly .cplocal
as well as the resulting relocations. Even if we rely on gcc to
expand these .cp*, we have to handle %gp_rel() and %neg().

> I think the change to gcc is minimum. That is
> we make sure that we don't use o64 for gcc. #2, #3, #4 and #5 will
> affect binutils.

I doubt anybody actually uses o64. I found several places in
binutils where it is broken or only partially implemented.


Thiemo

  reply	other threads:[~2001-08-27 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 17:38 Thiemo Seufer
2001-08-26 17:50 ` H . J . Lu
2001-08-26 18:02   ` Thiemo Seufer
2001-08-27 11:32     ` H . J . Lu
2001-08-27 11:44       ` Thiemo Seufer
2001-08-27 12:00         ` H . J . Lu
2001-08-27 12:41           ` Thiemo Seufer [this message]
2001-08-27 12:49             ` H . J . Lu
2001-08-27 13:13             ` Eric Christopher
2001-08-27 13:23               ` H . J . Lu
2001-08-31 20:11               ` Thiemo Seufer
2001-08-27 13:01           ` Andrew Cagney
2001-08-27 13:45             ` Thiemo Seufer
2001-08-27 14:06               ` Andrew Cagney
2001-08-28  8:52                 ` Thiemo Seufer
2001-09-06 14:34 ` Thiemo Seufer

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=20010827214105.E4669@rembrandt.csv.ica.uni-stuttgart.de \
    --to=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=binutils@sources.redhat.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).