Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org,  Nigel Stephens <nigel@mips.com>,
		  Chris Dearman <chris@mips.com>,
		  "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Use the address mask with addresses for SREC, etc.
Date: Wed, 25 Jul 2007 17:53:00 -0000	[thread overview]
Message-ID: <m3bqe0ig5t.fsf@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0707241740390.20726@perivale.mips.com> (Maciej W. Rozycki's message of "Tue, 24 Jul 2007 18:34:29 +0100 (BST)")


It's my understanding that addresses are signed on MIPS architectures,
and thus 32-bit SREC files are only capable of addressing locations
0xffffffff80000000 -- 0x000000007fffffff.  And that the issue you're
fixing here arises from BFD handing you addresses read from an SREC
file (which is using 32-bit addresses) in the 0x80000000 -- 0xffffffff
range.  Is that right?

I'm not too happy with complicating code in GDB because BFD is
providing it with the wrong addresses.  I have to imagine the same
thing would happen elsewhere.  When BFD reads the SREC file, does it
have any idea that it's a MIPS SREC file?  It looks like
bfd_get_sign_extend_vma doesn't know about MIPS SREC targets; would
fixing that, and then bfd/srec.c, help us get the right addresses into
the BFD?


  reply	other threads:[~2007-07-25 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 20:13 Maciej W. Rozycki
2007-07-25 17:53 ` Jim Blandy [this message]
2007-07-25 19:43   ` Maciej W. Rozycki
2007-07-27 20:41     ` Jim Blandy

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=m3bqe0ig5t.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=chris@mips.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=nigel@mips.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