From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/ARM] Framificate the ARM port [3/3]
Date: Mon, 07 Jul 2003 13:53:00 -0000 [thread overview]
Message-ID: <20030707135312.GB24634@nevyn.them.org> (raw)
In-Reply-To: <3F021836.6090809@redhat.com>
On Tue, Jul 01, 2003 at 07:24:38PM -0400, Andrew Cagney wrote:
> >Just in case you're wondering.
> >>
> >>This would break any architecture that didn't have an FP called "fp".
> >>This is because, "$fp" defaults to get_frame_base() ... :-(
> >
> >
> >Argh!
>
> :-)
>
> >get_frame_base_address defaults to get_frame_base; I could update
> >value_of_builtin_frame_fp_reg safely, I think. But I have no idea
> >where that would end up, so I'm going to defer to your judgement on
> >this if you've got a preference...
>
> kfail arm-*-* gdb/497?
>
> Having value_of_builtin_frame_fp_reg return get_frame_base_address is
> certainly more correct. The intent was for $fp to return the ABI's
> virtual frame base register.
>
> Try it.
>
> PS: ARM $fp confusion fixed?
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=479
No, not fixed. $fp will return the frame base now. What it should do,
IMO, is return $r11. Which isn't actually the frame pointer register
for Thumb mode, but that's the convention the assembler uses. Which
may then re-break the test until we fix this properly...
Richard, does that sound right? Andrew, have we got a standard
mechanism for register aliases, or would I need to create a
pseudo-register $fp that mapped onto $r11?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-07 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 22:55 Daniel Jacobowitz
2003-07-01 15:32 ` Andrew Cagney
2003-07-07 13:47 ` Daniel Jacobowitz
2003-07-07 14:46 ` Andrew Cagney
2003-07-07 21:12 ` Daniel Jacobowitz
2003-07-01 18:27 ` Andrew Cagney
2003-07-01 22:26 ` Daniel Jacobowitz
2003-07-01 23:24 ` Andrew Cagney
2003-07-07 13:53 ` Daniel Jacobowitz [this message]
2003-07-07 14:23 ` Daniel Jacobowitz
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=20030707135312.GB24634@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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