Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Split d10v-tdep.c into trad-frame.[hc]
Date: Sun, 08 Jun 2003 17:45:00 -0000	[thread overview]
Message-ID: <3EE37622.9080508@redhat.com> (raw)
In-Reply-To: <20030608165800.GA15675@nevyn.them.org>


>> +struct trad_frame

trad_frame_saved_regs?

>> +{
>> +  /* If non-zero (and regnum >= 0), the stack address at which the
>> +     register is saved.  By default, it is assumed that the register
>> +     was not saved (addr == 0).  Remember, a LONGEST can always fit a
>> +     CORE_ADDR.  */
>> +  LONGEST addr;
>> +  /* else, if regnum >=0 (and addr == 0), the REGNUM that contains
>> +     this registers value.  By default, it is assumed that the
>> +     registers are not moved (the register's value is still in that
>> +     register and regnum == the index).  */
>> +  int regnum;
>> +  /* else, if regnum < 0, ADDR is the registers value.  */
>> +};
> 
> 
> Gyuh?  I looked at this for a couple of minutes and couldn't make heads
> or tails of it until I went to look at trad-frame.c: this structure
> isn't a frame at all, it's a single saved register.  Could you rename
> it, and update the comments?
> 
> I'm also not sure I understand all the combinations:
>   regnum < 0, addr is the register value
>   regnum >= 0 and addr 0, regnum holds the new register number (in the
>     next frame?)

The previous frame's register is found in REGNUM in this frame.  Need to 
unwind the next frame's REGNUM to get the value of register REGNUM in 
this frame.

>   regnum >= 0 and addr non-zero, addr is the save address - but what's
>     regnum mean?  Nothing?

Nothing.

Andrew



  reply	other threads:[~2003-06-08 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 16:15 Andrew Cagney
2003-06-08 16:58 ` Daniel Jacobowitz
2003-06-08 17:45   ` Andrew Cagney [this message]
2003-06-08 17:48     ` Daniel Jacobowitz
2003-06-08 22:07       ` Andrew Cagney
2003-06-08 22:12         ` Daniel Jacobowitz

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=3EE37622.9080508@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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