From: Daniel Jacobowitz <dan@codesourcery.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for ARMv7M devices.
Date: Wed, 03 Nov 2010 13:17:00 -0000 [thread overview]
Message-ID: <20101103131734.GA5925@caradoc.them.org> (raw)
In-Reply-To: <4CD0D534.90701@eCosCentric.com>
On Wed, Nov 03, 2010 at 03:21:24AM +0000, Jonathan Larmour wrote:
> I think there's a more general issue here about whether it's expected to
> maintain support for existing working stub implementations such that they
> can be used as they have been used even when GDB is upgraded. Changing the
> interface with GDB remote stubs used to be a big no-no for GDB.
In general, I want to keep existing stubs working. But someone who
has access to an affected stub needs to lend a hand here; I don't and
can't test anything.
With stubs out there sending both FPA-regs+fake-CPSR and
FPA-regs+XPSR, I don't know how to make it work; in fact, I don't know
how FPA-regs+XPSR ever worked.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-11-03 13:17 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
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 [this message]
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=20101103131734.GA5925@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jifl@eCosCentric.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).