Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/wip] Save/restore cooked registers
Date: Mon, 26 Aug 2002 10:26:00 -0000	[thread overview]
Message-ID: <15722.22357.397126.473082@localhost.redhat.com> (raw)
In-Reply-To: <1020826155511.ZM30766@localhost.localdomain>

Kevin Buettner writes:
 > On Aug 25,  3:16pm, Andrew Cagney wrote:
 > 
 > > The attached is work-in-progress to get gdb saving just a subset of 
 > > cooked registers when doing things like an inferior function call.
 > 
 > Why is it necessary to save the cooked registers during an inferior
 > function call?  I would have thought that being able to save/restore
 > raw registers would be sufficient.
 > 
 > (Or did I miss a thread which explains this?)
 > 
 > Kevin


On ppc the e500 general registers are pseudo (i.e.cooked). Those
are used in inferior function calls, for parameter passing.
I think this is part of the story.
Full explanation:

http://sources.redhat.com/ml/gdb/2002-08/msg00196.html



Elena


  parent reply	other threads:[~2002-08-26 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 12:23 Andrew Cagney
2002-08-26  9:05 ` Kevin Buettner
2002-08-26  9:31   ` Andrew Cagney
2002-08-26 10:26   ` Elena Zannoni [this message]
2002-08-26 11:21     ` Kevin Buettner
2002-08-26 11:25       ` Andrew Cagney
2002-08-26 13:52         ` Kevin Buettner
2002-08-26 11:29       ` Elena Zannoni
2002-08-26 12:04         ` Kevin Buettner
2002-08-28  7:42         ` Richard Earnshaw
2002-08-28  9:58           ` Andrew Cagney
2002-08-29  8:36             ` Elena Zannoni

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=15722.22357.397126.473082@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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