From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
Fred Fish <fnf@intrinsity.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: MIPS sign extension of addresses
Date: Fri, 13 Sep 2002 00:36:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.1020913092432.21615A-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20020912153000.GA11343@nevyn.them.org>
On Thu, 12 Sep 2002, Daniel Jacobowitz wrote:
> > >I've not yet checked, but are there fundamental reasons why bfd_vma
> > >or CORE_ADDR have to be unsigned?
> >
> > I don't think it will help. I think it will also hinder the situtation
> > where BFD/GDB are supporting multiple architectures - one signed and one
> > unsigned.
>
> Oh, Andrew's right. Signed CORE_ADDR isn't viable because other
> architectures have and assume an unsigned address space.
Because MIPS is a minority? Well, I can see some reason here, but care
has to be taken not to lose a sign with casts when operating on MIPS
addresses. Fortunately the positive and the negative ranges of addresses
are distinct on MIPS so you won't find normal code or data crossing a
boundary (that might lead to wrong results of compare operations).
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2002-09-13 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 8:49 Fred Fish
2002-09-10 9:25 ` Paul Koning
2002-09-10 10:00 ` Maciej W. Rozycki
2002-09-10 9:57 ` Maciej W. Rozycki
2002-09-12 7:49 ` Fred Fish
2002-09-12 8:19 ` Andrew Cagney
2002-09-12 8:30 ` Daniel Jacobowitz
2002-09-13 0:36 ` Maciej W. Rozycki [this message]
2002-09-13 11:26 ` Andrew Cagney
2002-09-10 12:07 ` 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.GSO.3.96.1020913092432.21615A-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=ac131313@ges.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=fnf@intrinsity.com \
--cc=gdb@sources.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