From: Daniel Jacobowitz <dan@codesourcery.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: gdb-patches@sourceware.org, Kazu Hirata <kazu@codesourcery.com>
Subject: Re: Cortex-M CPSR thumb bit fix
Date: Fri, 09 Jul 2010 03:51:00 -0000 [thread overview]
Message-ID: <20100709035116.GB6577@caradoc.them.org> (raw)
In-Reply-To: <4C369AC0.5030408@eCosCentric.com>
On Fri, Jul 09, 2010 at 04:42:56AM +0100, Jonathan Larmour wrote:
> Hmm, that leads to the question: what if one says it's M and the other
> says it's something else? Personally I'd always go with what the actual
> binary being debugged says. Or at least that should override the XML
> definition. Although in that case the only benefit I can think of for the
> XML at all is connecting to a target when you don't have a binary to
> debug, which is rather a limited benefit.
It has to work the other direction, because the XML description
typically comes from the target stub / agent. So we consider that the
definitive statement on target capabilities.
> > Jonathan, Kazu, anyone have a preference on producing a combined patch?
>
> I haven't mucked around with the XML stuff before, so if you do want a
> combined patch, perhaps Kazu could look, particularly as there were also
> unresolved comments on his patch, and none of the XML side was posted.
> Hopefully with my patch fixed with your comments, then I'm reducing the
> effort to combine at least.
Thanks, I really appreciate it! Either I'll talk Kazu into looking at
it, or find some time to do so myself.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-07-09 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 19:26 Jonathan Larmour
2010-07-08 21:37 ` Daniel Jacobowitz
2010-07-09 3:43 ` Jonathan Larmour
2010-07-09 3:51 ` Daniel Jacobowitz [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=20100709035116.GB6577@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jifl@eCosCentric.com \
--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