From: Alan Modra <alan@linuxcare.com.au>
To: Ulf Carlsson <ulfc@calypso.engr.sgi.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
BINUTILS Patches <binutils@sourceware.cygnus.com>,
GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [rfc] For mips, sign-extended ecoff offsets
Date: Mon, 19 Jun 2000 18:57:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0006201151180.12273-100000@front.linuxcare.com.au> (raw)
In-Reply-To: <14670.52424.697477.308492@calypso.engr.sgi.com>
On Mon, 19 Jun 2000, Ulf Carlsson wrote:
> On a 64-bit MIPS processor 32-bit addresses are of course sign
> extended, but this shouldn't concern the 32-bit BFD backend for MIPS
> in any way. Whether we sign extend the addresses or not shouldn't
> make any difference except in our internal representation of the
> bfd_vma. I may be wrong though!
It doesn't make much difference if bfd_vma is only 32-bits (ie. BFD_64 is
not set) Where you get into trouble is with targets that are generally
32-bit, but you may be using 64-bit bfd_vma types due to --enable-targets
--
Linuxcare. Support for the Revolution.
next parent reply other threads:[~2000-06-19 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0006200100160.12273-100000@front.linuxcare.com.au>
[not found] ` <394EC637.24300B87@cygnus.com>
[not found] ` <14670.52424.697477.308492@calypso.engr.sgi.com>
2000-06-19 18:57 ` Alan Modra [this message]
[not found] ` <200006200307.UAA10516@localhost.cygnus.com>
[not found] ` <20000620034102.18244.qmail@daffy.airs.com>
2000-06-25 14:13 ` Ralf Baechle
[not found] <Pine.LNX.4.21.0006201128050.12273-100000@front.linuxcare.com.au>
[not found] ` <20000620033908.18201.qmail@daffy.airs.com>
[not found] ` <39531146.4B99A64B@cygnus.com>
[not found] ` <20000623153232.1843.qmail@daffy.airs.com>
2000-07-03 23:47 ` Andrew Cagney
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=Pine.LNX.4.21.0006201151180.12273-100000@front.linuxcare.com.au \
--to=alan@linuxcare.com.au \
--cc=ac131313@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=ulfc@calypso.engr.sgi.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