From: Ian Lance Taylor <ian@zembu.com>
To: mark@codesourcery.com
Cc: geoffk@ozemail.com.au, gavin@cygnus.com,
binutils@sourceware.cygnus.com, brendan@cygnus.com
Subject: Re: Reloc changes to bfd/elf32-mips.c
Date: Wed, 29 Sep 1999 08:25:00 -0000 [thread overview]
Message-ID: <19990929152418.26943.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990928222137W.mitchell@codesourcery.com>
From: Mark Mitchell <mark@codesourcery.com>
Date: Tue, 28 Sep 1999 22:21:37 -0700
I think it's OK to have `ld' (as an extension) handle this case. But,
we really should fix GAS. It would be useful (I know this because
customers have told me so :-)) to be able to assemble things with GAS,
but link them with the MIPS linker. The .o files that GAS creates are
not ABI-compliant, and not for any particularly good reason. (In
other words, I don't see a real performance improvement/useful feature
that the "incorrect" ordering buys you.)
Yeah, I guess we fix up unmatched %hi relocs, but we don't bother to
ensure that we don't have a leading %lo reloc. If anybody wants to
fix this, the code is in mips_frob_file in gas/config/tc-mips.c.
Ian
next prev parent reply other threads:[~1999-09-29 8:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 4:30 Geoff Keating
1999-09-27 12:37 ` Mark Mitchell
1999-09-28 0:54 ` Mark Mitchell
1999-09-28 6:57 ` Ian Lance Taylor
1999-09-28 20:32 ` Geoff Keating
1999-09-28 20:57 ` Ian Lance Taylor
1999-09-28 21:52 ` Geoff Keating
1999-09-28 22:03 ` Ian Lance Taylor
1999-10-06 19:21 ` Geoff Keating
1999-10-06 19:35 ` Ian Lance Taylor
1999-10-06 20:39 ` Geoff Keating
1999-10-06 20:53 ` Ian Lance Taylor
1999-10-07 4:47 ` Geoff Keating
1999-10-07 7:28 ` Ian Lance Taylor
1999-10-07 9:17 ` Mark Mitchell
1999-09-28 22:16 ` Mark Mitchell
1999-09-29 8:25 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-27 4:24 Geoff Keating
1999-09-27 18:25 ` Ian Lance Taylor
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=19990929152418.26943.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=brendan@cygnus.com \
--cc=gavin@cygnus.com \
--cc=geoffk@ozemail.com.au \
--cc=mark@codesourcery.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).