This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: read_register_byte can't work with pseudo-reg model
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: Elena Zannoni <ezannoni at redhat dot com>, gdb at sources dot redhat dot com
- Date: Thu, 16 May 2002 09:41:20 -0400
- Subject: Re: read_register_byte can't work with pseudo-reg model
- References: <200205161219.NAA16585@cam-mail2.cambridge.arm.com>
> I'm guessing. Try:
>>
>> if (REGISTER_READ_P ())
>> {
>> do something fairly sane;
>> }
>> else
>> {
>> all the legacy cruft including the call to
>> legacy_read_register_gen() and that test.
>> }
>>
>> Thing is that there is only one target in the FSF using
>> READ_REGISTER_P() so there is this dividing line - something using
>> read_register_p() can be given far stronger requirements than for the
>> older code.
>
>
> Which target is that, and where is READ_REGISTER_P ? I can't find
> anything in the either the source or the mailing lists. Mind you, the
> web-based mailing list search even fails to find your message when I
> search for READ_REGISTER_P.
Sorry, register_read_p() -> sh5.
(something else on my todo list is stomp on some of these redundant
interfaces :-)
Andrew