This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/cagney_regbuf-20020515-branch] Really separate out oldandnew
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 28 May 2002 18:49:36 -0400
- Subject: Re: [patch/cagney_regbuf-20020515-branch] Really separate out oldandnew
- References: <3CED2E95.3080102@cygnus.com> <3CEED117.9C727CF0@redhat.com>
> In addition, the regcache code only calls legacy_*() functions when
>> ->legacy_p. The new code goes straight through.
>>
>> I think I'm about done with that branch. I'll next post a full patch
>> and figure out how to get something equivalent into the trunk. More
>> importantly, how to do it without breaking SH5.
>>
>> enjoy,
>> Andrew
>
>
> OK -- I was trying to ignore this, but it breaks one of my targets.
> What do I have to do, to make my old target use the old legacy method?
In the short term, you shouldn't need to do anything. All the old
targets will still use the old mechanisms and those mechanisms will
allow the storage of pseudo-registers in the register cache.
Long term, the target will probably need to be updated so that it uses
gdbarch_register_read/write.
enjoy,
Andrew