From: Richard Sandiford <rsandifo@redhat.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>,
linux-mips@linux-mips.org
Subject: Re: Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5
Date: Tue, 24 May 2005 11:50:17 +0100 [thread overview]
Message-ID: <871x7w99ue.fsf@firetop.home> (raw)
In-Reply-To: <Pine.LNX.4.61L.0505241122290.13738@blysk.ds.pg.gda.pl> (Maciej W. Rozycki's message of "Tue, 24 May 2005 11:40:53 +0100 (BST)")
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
> Trying to support GNU extensions in ECOFF is probably hopeless and not
> worth the hassle and the file format is likely to be obsoleted by the
> toolchain soon (if not already done), except from BFD -- which'll let you
> continue doing `objcopy', `objdump', etc.
Yeah. It's probably also worth noting that we might (soon?) remove the
-mno-explicit-relocs/-mno-split-addresses mode from gcc. Having both
modes does add to the maintenance burden and the gas support for PIC
relocation operators has been around for a while now. (It dates back
to binutils 2.14 IIRC.)
Richard
next prev parent reply other threads:[~2005-05-24 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 7:10 Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5 Stanislaw Skowronek
2005-05-23 11:17 ` Richard Sandiford
2005-05-23 16:19 ` Stanislaw Skowronek
2005-05-23 17:23 ` Richard Sandiford
2005-05-23 17:32 ` Stanislaw Skowronek
2005-05-24 6:35 ` Richard Sandiford
2005-05-24 6:39 ` Stanislaw Skowronek
2005-05-24 6:56 ` Richard Sandiford
2005-05-24 6:58 ` Stanislaw Skowronek
2005-05-24 10:40 ` Maciej W. Rozycki
2005-05-24 10:47 ` Stanislaw Skowronek
2005-05-24 11:40 ` Maciej W. Rozycki
2005-05-24 10:50 ` Richard Sandiford [this message]
2005-05-24 14:22 ` Ralf Baechle
2005-05-24 14:50 ` Maciej W. Rozycki
2005-05-24 15:00 ` Ralf Baechle
2005-05-24 15:04 ` Maciej W. Rozycki
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=871x7w99ue.fsf@firetop.home \
--to=rsandifo@redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=sskowron@ET.PUT.Poznan.PL \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.