Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@intrinsity.com>
To: macro@ds2.pg.gda.pl (Maciej W. Rozycki)
Cc: fnf@intrinsity.com (Fred Fish),
	binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: MIPS sign extension of addresses
Date: Thu, 12 Sep 2002 07:49:00 -0000	[thread overview]
Message-ID: <200209121449.g8CEnmL09055@beeville.vert.intrinsity.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1020910185152.23871F-100000@delta.ds2.pg.gda.pl> from "Maciej W. Rozycki" at Sep 10, 2002 06:57:49 PM

>  Well, that seems the reason of the trouble -- for MIPS addresses in
> object and executable files should be treated as signed and bfd_vma should
> be a signed type since that's how MIPS works. 

So does that mean that it would be more desirable if the MIPS ports used
signed long long for bfd_vma/CORE_ADDR instead of unsigned long long?

I'm willing to work on making that happen if that is the consensus for
making MIPS support more consistent with how the hardware works.

I've not yet checked, but are there fundamental reasons why bfd_vma
or CORE_ADDR have to be unsigned?

-Fred


  reply	other threads:[~2002-09-12 14:49 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 [this message]
2002-09-12  8:19     ` Andrew Cagney
2002-09-12  8:30       ` Daniel Jacobowitz
2002-09-13  0:36         ` Maciej W. Rozycki
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=200209121449.g8CEnmL09055@beeville.vert.intrinsity.com \
    --to=fnf@intrinsity.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=macro@ds2.pg.gda.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox