Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, 	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [rfc] dwarf2 unwinder and MIPS n32
Date: Mon, 30 Apr 2007 13:26:00 -0000	[thread overview]
Message-ID: <20070430132118.GC25539@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0704301335560.20399@perivale.mips.com>

On Mon, Apr 30, 2007 at 01:40:54PM +0100, Maciej W. Rozycki wrote:
> On Sat, 28 Apr 2007, Daniel Jacobowitz wrote:
> 
> > Maybe if the size of the register != the size of a void * we should
> > store it as an unsigned integer.  But that seems hackish to me.
> 
>  Of course MIPS addresses are signed, so if you have a stack pointer in 
> KSEG0 (e.g. 0x8fff0000), you want to store it as a signed integer, don't 
> you?

It should already be sign extended at this point; CORE_ADDR will be a
64-bit type and it should be set to 0xffffffff_8fff0000 by read_reg.
That's the only reason we can get away with it.

>  Anyway, I have the following patch waiting in the queue for submission -- 
> perhaps it is less hackish. ;-)

Ewww.  Sorry, this one's even worse than mine :-) Let's not abuse our
types that way.  I have a nicer patch now based on Ulrich's
suggestion.  I'll post it in a few minutes when testing finishes (or a
little later if I can figure out where to get that board file you
mentioned).

> 2007-04-30  Maciej W. Rozycki  <macro@mips.com>
> 
> 	* dwarf2-frame.c (read_reg): Extract an address using the width
> 	of the register to be used to hold it as the size.

I see the read_reg part of this patch has been updated to apply to
HEAD, but do you know if it is older than this change?  If so, it's
probably not necessary anymore.

2006-05-17  Daniel Jacobowitz  <dan@codesourcery.com>

        * dwarf2-frame.c: Include "value.h".
        (read_reg): Use unpack_long and register_type.
        * Makefile.in (dwarf2-frame.o): Update.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-30 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 20:42 Daniel Jacobowitz
2007-04-28 22:52 ` Ulrich Weigand
2007-04-30 13:28   ` Daniel Jacobowitz
2007-04-30 20:19     ` Ulrich Weigand
2007-05-14 17:22       ` Daniel Jacobowitz
2007-04-30 13:00 ` Maciej W. Rozycki
2007-04-30 13:26   ` Daniel Jacobowitz [this message]
2007-04-30 13:44     ` Maciej W. Rozycki

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=20070430132118.GC25539@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@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