From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: gdb-patches@sourceware.org, pinskia@gmail.com,
catalin.udma@freescale.com
Subject: Re: [PATCH] aarch64-core.xml: 32-bit cpsr -> 64-bit pstate
Date: Tue, 08 Sep 2015 08:45:00 -0000 [thread overview]
Message-ID: <55EEA028.9000000@redhat.com> (raw)
In-Reply-To: <86si6p726k.fsf@gmail.com>
On 09/08/2015 09:20 AM, Yao Qi wrote:
>
> AArch64 is still a new architecture, and there isn't much compatibility
> burden as other old archs have.
Under the same reasoning, you should be able to fix kgdb as well.
> Under this context, I think correctness
> is more important than compatibility. If we don't fix it now, we can't fix
> it forever. So it isn't an arbitrary change.
Simply cpsr->pstate like in your patch has user-visible changes as well. Do
users really expect to see "pstate" in "info registers"? If it really OK
that "print $cpsr" stops working?
But the change is really not OK as is. You can't have a server _not_
send "cpsr" and claim that the target description supports
the "org.gnu.gdb.aarch64.core" feature:
@node AArch64 Features
@subsection AArch64 Features
@cindex target descriptions, AArch64 features
The @samp{org.gnu.gdb.aarch64.core} feature is required for AArch64
targets. It should contain registers @samp{x0} through @samp{x30},
@samp{sp}, @samp{pc}, and @samp{cpsr}.
If we do go the cpsr->pstate direction, we'll have to add a new
target feature.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-09-08 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 12:56 Yao Qi
2015-09-07 22:46 ` Richard Earnshaw
2015-09-08 8:20 ` Yao Qi
2015-09-08 8:45 ` Pedro Alves [this message]
2015-09-08 10:06 ` Yao Qi
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=55EEA028.9000000@redhat.com \
--to=palves@redhat.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=catalin.udma@freescale.com \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.com \
--cc=qiyaoltc@gmail.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