From: Terry Guo <gnu.terry@gmail.com>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: gdb-patches@sourceware.org, Ilija Kocho <ilijak@siva.com.mk>,
Terry Guo <terry.guo@arm.com>
Subject: Re: [patch] Add support for VFP d16 layout for Cortex-M4
Date: Thu, 19 Apr 2012 16:38:00 -0000 [thread overview]
Message-ID: <CAMCN_Bi4U+faBvu6Wd2WryNrGMzyf5bcpGAa2rYmkEdHWGaing@mail.gmail.com> (raw)
In-Reply-To: <4F9035F4.7060101@eCosCentric.com>
On Thu, Apr 19, 2012 at 11:57 PM, Jonathan Larmour <jifl@ecoscentric.com> wrote:
>
> STM32F4 is likely to follow very soon after. Ironically, it's not likely
> to be committed until we have some confidence that what goes into GDB will
> match up with what the stub is doing! We wouldn't want to commit something
> that has to change in an incompatible way.
>
Agree. I am also worrying about the gdb stub. If they return something
different from what we currently expect, we will have to make another
change. So I am talking to OpenOCD to share with them what the gdb is
going to do. There are many other gdb stub vendors like JLink. I plan
to talk with them and hope to achieve some consensus between GDB and
stub.
BR,
Terry
next prev parent reply other threads:[~2012-04-19 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 15:13 Jonathan Larmour
2012-04-19 15:58 ` Terry Guo
2012-04-19 16:09 ` Jonathan Larmour
2012-04-19 16:38 ` Terry Guo [this message]
2012-04-19 17:30 ` Jonathan Larmour
2012-04-20 7:51 ` Ilija Kocho
2012-04-20 8:31 ` Terry Guo
2012-04-20 8:54 ` Ilija Kocho
2012-04-20 11:44 ` Pedro Alves
2012-04-20 12:43 ` Pedro Alves
2012-04-20 13:20 ` Terry Guo
2012-04-20 13:22 ` Pedro Alves
2012-04-24 2:49 ` Jonathan Larmour
2012-04-26 20:28 ` Tom Tromey
2012-04-26 23:40 ` Jonathan Larmour
2012-04-27 15:55 ` Tom Tromey
2012-04-26 7:35 ` Sergio Durigan Junior
2012-04-26 15:07 ` Jonathan Larmour
2012-04-26 15:20 ` Pedro Alves
2012-04-26 15:29 ` Jonathan Larmour
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=CAMCN_Bi4U+faBvu6Wd2WryNrGMzyf5bcpGAa2rYmkEdHWGaing@mail.gmail.com \
--to=gnu.terry@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ilijak@siva.com.mk \
--cc=jifl@ecoscentric.com \
--cc=terry.guo@arm.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