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: Fri, 27 Jul 2007 20:41:00 -0000	[thread overview]
Message-ID: <m38x91oaup.fsf@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0707251850310.27010@perivale.mips.com> (Maciej W. Rozycki's message of "Wed, 25 Jul 2007 19:11:49 +0100 (BST)")


"Maciej W. Rozycki" <macro@mips.com> writes:
> On Wed, 25 Jul 2007, Jim Blandy wrote:
>> 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?
>
>  Well, AFAICS SREC and HEX files are target-agnostic, much like "binary" 
> BFD.  The only possible way of handling it in BFD itself would be by 
> sign-extending addresses at the "right point" if the destination BFD 
> implies bfd_get_sign_extend_vma() true.  I somehow dislike hardcoding the 
> "right point" in {ihex,srec,tekhex}.c, but given these formats appear to 
> me as pure 32-bit, perhaps chosing bit 31 as the "right point" is OK.  
> What do you think?

For srec.c, that seems reasonable to me.  The logic there for writing
records will always output "negative" addresses as 32-bit values ---
it does not assume that s-records with two- or three-byte addresses
will be sign-extended from those lengths.  I haven't looked at ihex or
texhex.

The binutils folks will be the ones to approve the BFD changes, so
before you dive into this, you might want to explain your situation
there and get their general approval.  They might even have better
ideas.  :)


      reply	other threads:[~2007-07-27 20:22 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
2007-07-25 19:43   ` Maciej W. Rozycki
2007-07-27 20:41     ` Jim Blandy [this message]

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=m38x91oaup.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