From: "H . J . Lu" <hjl@lucon.org>
To: Richard Henderson <rth@redhat.com>
Cc: David B Anderson <davea@quasar.engr.sgi.com>,
gdb@sourceware.cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Why does mips define elf_backend_sign_extend_vma to true?
Date: Tue, 07 Aug 2001 23:21:00 -0000 [thread overview]
Message-ID: <20010807232102.A19636@lucon.org> (raw)
In-Reply-To: <20010807224622.A25295@redhat.com>
On Tue, Aug 07, 2001 at 10:46:22PM -0700, Richard Henderson wrote:
> On Tue, Aug 07, 2001 at 10:04:51PM -0700, H . J . Lu wrote:
> > I think the better fix is to check the EF_MIPS field to only
> > do sign extension for MIPS III/IV. But we don't support such encoding.
>
> There are too many odd combinations of mips chips for
> something so simplistic to work.
>
> Besides, things aren't broken. Use a 64-bit BFD and
> you _should_ get sign-extension for MIPS.
>
That is wrong for MIPS I/II even if BFD is 64bit for whatever reason.
In any case, I won't bother with any patches. But I will fix it in my
Linux binutils.
H.J.
next prev parent reply other threads:[~2001-08-07 23:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 20:27 David B Anderson
2001-08-07 22:04 ` H . J . Lu
2001-08-07 22:46 ` Richard Henderson
2001-08-07 23:21 ` H . J . Lu [this message]
2001-08-08 0:50 ` Richard Henderson
2001-08-08 1:09 ` Maciej W. Rozycki
2001-08-08 7:29 ` H . J . Lu
2001-08-08 7:50 ` Andrew Cagney
2001-08-08 8:03 ` H . J . Lu
2001-08-08 8:18 ` Andrew Cagney
2001-08-08 9:02 ` H . J . Lu
2001-08-08 9:53 ` Daniel Jacobowitz
2001-08-08 10:02 ` H . J . Lu
2001-08-08 11:02 ` Daniel Jacobowitz
2001-08-08 11:08 ` H . J . Lu
2001-08-09 12:23 ` Andrew Cagney
2001-08-08 9:48 ` Daniel Jacobowitz
2001-08-08 9:52 ` H . J . Lu
2001-08-10 0:47 ` Maciej W. Rozycki
[not found] <20010807182459.A15252@lucon.org>
[not found] ` <20010807183933.A15425@lucon.org>
[not found] ` <3B709900.3000502@cygnus.com>
[not found] ` <20010807184504.A15571@lucon.org>
2001-08-07 18:52 ` H . J . Lu
2001-08-07 18:58 ` Daniel Jacobowitz
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=20010807232102.A19636@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=davea@quasar.engr.sgi.com \
--cc=gdb@sourceware.cygnus.com \
--cc=rth@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