From: Richard Earnshaw <Richard.Earnshaw@buzzard.freeserve.co.uk>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Kazu Hirata <kazu@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Add support for ARMv7M devices.
Date: Thu, 24 Jun 2010 20:04:00 -0000 [thread overview]
Message-ID: <4C23BA28.80106@buzzard.freeserve.co.uk> (raw)
In-Reply-To: <20100624164149.GD8410@caradoc.them.org>
On 24/06/10 17:41, Daniel Jacobowitz wrote:
>
> On Thu, Jun 10, 2010 at 12:04:43AM +0100, Richard Earnshaw wrote:
>> It looks to me as though this code should also mostly apply to ARMv6M
>> as well (coretex-m0/1). However, the choice of name
>> 'org.gnu.gdb.arm.core-v7m' seems to suggest otherwise. Is there
>> really a difference between the support needed for these cores? Or
>> would a more suitable name be appropriate?
>
> Historical note: it's this way because the patch predated v6m. We
> need to support the v7m name internally for compatibility, but we
> can rename the official version if you like.
>
> I can imagine GDB wanting to know about BASEPRI / FAULTMASK. But we
> provide the privileged registers in another "feature" today, and use
> this core-v7m feature with both v6-m and v7-m. So
> 'org.gnu.gdb.amr.core-m' instead?
>
I'd suggest
org.gnu.gdb.arm.m-profile
next prev parent reply other threads:[~2010-06-24 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 14:03 Kazu Hirata
2010-06-09 22:29 ` Doug Evans
2010-06-09 23:04 ` Richard Earnshaw
2010-06-24 16:42 ` Daniel Jacobowitz
2010-06-24 20:04 ` Richard Earnshaw [this message]
2010-08-16 18:06 ` Daniel Jacobowitz
2010-08-17 9:00 ` Matthew Gretton-Dann
2010-08-24 15:56 ` Daniel Jacobowitz
2010-10-29 23:47 ` Jonathan Larmour
2010-11-01 3:40 ` Daniel Jacobowitz
2010-11-03 3:21 ` Jonathan Larmour
2010-11-03 13:17 ` Daniel Jacobowitz
2010-11-10 2:21 ` Jonathan Larmour
2010-06-10 8:56 ` Matthew Gretton-Dann
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=4C23BA28.80106@buzzard.freeserve.co.uk \
--to=richard.earnshaw@buzzard.freeserve.co.uk \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=kazu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).