From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: uweigand@de.ibm.com, rearnsha@arm.com, yao@codesourcery.com,
gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Implement gdbarch hook user_register_name on ARM
Date: Thu, 23 Dec 2010 12:08:00 -0000 [thread overview]
Message-ID: <201012230927.oBN9R86R013591@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20101223031853.GM2596@adacore.com> (message from Joel Brobecker on Thu, 23 Dec 2010 07:18:53 +0400)
> Date: Thu, 23 Dec 2010 07:18:53 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> > However, there is no defined way to *query* that value. Therefore,
> > my understanding is that the MI frontends typically query the value
> > of the standard "fp" register to retrieve this value. If an architecture
> > back-end now goes and redefines what "fp" stands for, this will break
> > this MI frontend convention ...
>
> I am not sure I understand the problem. Could we use "get_frame_base"
> instead?
As far as I know, that is exactly what happens when you *don't* set
deprecated_fp_regnum, and you don't have a "hard" frame pointer
register explicitly named "fp".
See std-reg.c:value_of_builtin_frame_fp_reg().
Really, if arm can get away with not setting deprecated_fp_regnum(),
we should go for it.
prev parent reply other threads:[~2010-12-23 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 10:22 [patch 1/2] New gdbarch hook user_register_name Yao Qi
2010-12-15 10:48 ` [patch 2/2] Implement gdbarch hook user_register_name on ARM Yao Qi
2010-12-21 19:07 ` Ulrich Weigand
2010-12-22 17:44 ` Yao Qi
2010-12-22 18:12 ` Mark Kettenis
2010-12-23 7:19 ` Yao Qi
2010-12-23 1:54 ` Ulrich Weigand
2010-12-23 4:10 ` Yao Qi
2010-12-23 18:37 ` Ulrich Weigand
2010-12-24 5:16 ` Yao Qi
2010-12-28 14:52 ` Ulrich Weigand
2010-12-22 17:54 ` Richard Earnshaw
2010-12-23 2:05 ` Ulrich Weigand
2010-12-23 3:37 ` Joel Brobecker
2010-12-23 12:08 ` Mark Kettenis [this message]
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=201012230927.oBN9R86R013591@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=rearnsha@arm.com \
--cc=uweigand@de.ibm.com \
--cc=yao@codesourcery.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