public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: FP aliases
Date: Thu, 29 May 2003 19:49:00 -0000	[thread overview]
Message-ID: <3ED6644D.2030201@solidas.com> (raw)
In-Reply-To: <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

  reply	other threads:[~2003-05-29 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 23:46 Svein E. Seldal
2003-05-29 16:11 ` Andrew Cagney
2003-05-29 19:49   ` Svein E. Seldal [this message]
2003-05-29 20:01     ` Andrew Cagney
2003-05-29 20:41       ` Svein E. Seldal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ED6644D.2030201@solidas.com \
    --to=svein.seldal@solidas.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).