This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch/wip] Save/restore cooked registers


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]