This is the mail archive of the
mailing list for the GCC project.
Re: SH5 compact register numbering in gcc -> gdb interface
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: joern dot rennecke at st dot com
- Cc: ezannoni at redhat dot com, gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com,aoliva at redhat dot com, bje at redhat dot com
- Date: Tue, 07 May 2002 13:13:01 -0400
- Subject: Re: SH5 compact register numbering in gcc -> gdb interface
- References: <3CCED903.294513BE@st.com> <firstname.lastname@example.org> <3CD12BF8.7E1650C1@st.com>
> sh-tdep has a lot of hardcoded 'knowledge' how simulator numbers relate
> to the layout of th register cache. Moreover, we should loose all the
> tdep->FOO_REGNUM stuff where the value is actually a constant according
> to the simulator interface.
Just FYI, the thing that controls the internal register layout of GDB is
[currently] the remote protocol. If you try to wire down GDB's internal
register numbers to match the simulator, you'll likely break GDB's
compatibility with existing remote targets.
While this limitation is being worked on, it doesn't affect the GDB <->
sim maping - that can already be adjusted independant of the other
register numbering schema.