Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: IBM S/390 prologue analysis revisited
Date: Wed, 02 Jul 2003 19:20:00 -0000	[thread overview]
Message-ID: <20030702192002.GB26551@nevyn.them.org> (raw)
In-Reply-To: <3F032568.5060700@redhat.com>

On Wed, Jul 02, 2003 at 02:33:12PM -0400, Andrew Cagney wrote:
> 
> >>Editor note: It's missing the undefined state.  I'll add it.
> >
> >
> >I'd say that 'struct trad_frame_saved_reg' and 'struct prologue_value'
> >are inverses of each other.  They represent information at different
> >steps in the process:
> >- First you interpret your prologue to get a bunch of prologue values.
> >- Then you use those to compute a set of trad_frame_saved_reg values.
> >- Finally, those are what you'd use to find registers.
> >
> >Let me explain what I mean.
> 
> Ah!  Yes, in that case my suggestion doesn't make sense.
> 
> Can I encourage you to add this to either the s390 to trad-frame code? 
> Trad frame might be better as it then provides a pointer towards the 
> ``new technique'' (but which ever).

Yeah, I'd like to see the new code outside of s390-tdep.c also.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-02 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vt2d6gv2lt3.fsf@zenia.home>
     [not found] ` <1030630233621.ZM27669@localhost.localdomain>
2003-07-01  0:14   ` Elena Zannoni
2003-07-01  0:57 ` Andrew Cagney
2003-07-01 12:28   ` Andrew Cagney
2003-07-02  0:06     ` Jim Blandy
2003-07-02 18:33       ` Andrew Cagney
2003-07-02 19:20         ` Daniel Jacobowitz [this message]
2003-07-01 22:51   ` 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=20030702192002.GB26551@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@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