This is the mail archive of the
mailing list for the GCC project.
Re: SH5 compact register numbering in gcc -> gdb interface
- From: Joern Rennecke <joern dot rennecke at st dot com>
- To: ezannoni at redhat dot com
- Cc: gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, aoliva at redhat dot com,bje at redhat dot com, ac131313 at cygnus dot com
- Date: Thu, 02 May 2002 11:13:46 +0100
- Subject: Re: SH5 compact register numbering in gcc -> gdb interface
- Organization: SuperH UK Ltd.
- References: <3CCED903.294513BE@st.com> <3CCEEBC6.5959E2FD@st.com> <firstname.lastname@example.org>
- Reply-to: joern dot rennecke at st dot com
> This can be worked around in gdb with
> STAB_REG_TO_REGNUM/DWARF2_REG_TO_REGNUM functions. Other targets do
OK, but I see no point in setting up such a mapping when there is
no data it would operate on.
> > This shouldn't really matter since these registers should
> > not appear in debug information with the ABIs currently
> > in use. It is confusing, however, that gcc pretends that
> > this is part of the interface. I therefore propose to remove
> > mappings for T and GDB from SH_DBX_REGISTER_NUMBER.
> I am not sure I understand your last sentence. You want to remove T
> from the mapping? It is not strictly necessary.
The presense of T and gdb in the mapping is just confusing, since there
is no interface for these registers between gcc and gdb at the present,
and no reason for it to be. If we ever think we have to put a user variable
into T and/or gbr, and express this in debug information, we can still pick
a number, and make it consistent between gcc and gdb at the same time.
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330