This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/wip] Save/restore cooked registers
- From: Elena Zannoni <ezannoni at redhat dot com>
- To: Kevin Buettner <kevinb at redhat dot com>
- Cc: Andrew Cagney <ac131313 at ges dot redhat dot com>,gdb-patches at sources dot redhat dot com
- Date: Mon, 26 Aug 2002 12:29:09 -0400
- Subject: Re: [patch/wip] Save/restore cooked registers
- References: <3D692D27.4010003@ges.redhat.com><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