From: Alexandre Oliva <aoliva@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: DJ Delorie <dj@redhat.com>, ian@airs.com, binutils@sources.redhat.com
Subject: Re: [patch] new sh relocs
Date: Sat, 16 Aug 2003 15:21:00 -0000 [thread overview]
Message-ID: <or3cg139xw.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030816135520.GL27145@bubble.sa.bigpond.net.au>
On Aug 16, 2003, Alan Modra <amodra@bigpond.net.au> wrote:
> On Sat, Aug 16, 2003 at 09:38:45AM -0400, DJ Delorie wrote:
>>
>> > But, but, isn't moving relocs going to break existing object files?
>>
>> Sad but true. At least it's only objects built with relax on.
>> Renesas noted such incompatibility in their request to us.
> You need to reject old objects then. EI_OSABI and EI_ABIVERSION were
> designed for exactly this purpose.
Unfortunately we're the ones that got the ABI wrong, and Renesas tools
don't emit any EI_* markers we could use to tell, so we should just
take the risk and change the meaning of relocs we've been generating
with the wrong meaning.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-08-16 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 20:51 DJ Delorie
2003-08-16 5:19 ` Ian Lance Taylor
2003-08-16 13:38 ` DJ Delorie
2003-08-16 13:55 ` Alan Modra
2003-08-16 14:04 ` DJ Delorie
2003-08-16 15:21 ` Alexandre Oliva
2003-08-16 15:21 ` Alexandre Oliva [this message]
2003-08-25 18:37 ` DJ Delorie
2003-09-06 0:07 ` DJ Delorie
2003-09-06 6:59 ` Nick Clifton
2003-09-10 7:56 ` Alexandre Oliva
2003-09-10 16:45 ` DJ Delorie
2003-09-24 2:28 ` DJ Delorie
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=or3cg139xw.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=ian@airs.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).