This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: FP aliases
- From: "Svein E. Seldal" <Svein dot Seldal at solidas dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 29 May 2003 21:49:33 +0200
- Subject: Re: FP aliases
- References: <3ED54A80.3030900@solidas.com> <3ED63129.9020500@redhat.com>
Andrew Cagney wrote:
If your architecture does not have a $fp, do not try to provide it. GDB
will map $fp onto the frame's base address (as defined by the debug info).
<snip>
Only include $fp in the register names when there is a register, as
defined by the ISA, that has the name "fp".
The d10v doesn't have a register called FP, so doesn't provide "fp".
Instead, $fp is mapped onto the frame's base address.
Well, the trick is that tic4x-gcc assigns ar3 as an fp register (at all
times), so you wind up stuck in the middle here. You have an FP-like
register, yet it's not named FP.
But I've rough-ported the d10v unwind mechanisms to the tic4x port, and
it seems like I am able to work it out without the fp register. (Still,
I need to understand those unwind things..)
Yes. An architecture function is deprecated when either: it isn't
needed at all (as with FP_REGNUM, READ_FP); or has been made redundant
by a newer mechanism.
Yes, and its these new mechanisms I'm trying to work out. I'll take a
look at the i386 port, and see if I'm able to resolve its functionality
from that.
Svein