From: Andrew Cagney <ac131313@redhat.com>
To: "Svein E. Seldal" <Svein.Seldal@solidas.com>
Cc: gdb@sources.redhat.com
Subject: Re: FP aliases
Date: Thu, 29 May 2003 20:01:00 -0000 [thread overview]
Message-ID: <3ED66705.3080100@redhat.com> (raw)
In-Reply-To: <3ED6644D.2030201@solidas.com>
> Well, the trick is that tic4x-gcc assigns ar3 as an fp register (at all times),
What of -fomit-frame-pointer? GDB's past mistake was to assume, as your
suggesting, that $fp is always a hard register. Unfortunatly, GCC
eventually got better ideas (and eliminated that assumption) causing GDB
to fall apart.
> 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.
Yes, GDB's FP isn't a real register.
Andrew
next prev parent reply other threads:[~2003-05-29 20:01 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
2003-05-29 20:01 ` Andrew Cagney [this message]
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=3ED66705.3080100@redhat.com \
--to=ac131313@redhat.com \
--cc=Svein.Seldal@solidas.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).