Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Terry Guo <gnu.terry@gmail.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 17:30:00 -0000	[thread overview]
Message-ID: <4F90444C.5030505@eCosCentric.com> (raw)
In-Reply-To: <CAMCN_Bi4U+faBvu6Wd2WryNrGMzyf5bcpGAa2rYmkEdHWGaing@mail.gmail.com>

On 19/04/12 17:18, Terry Guo wrote:
> 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.

I think there's probably very little variation in what would make sense.
Ultimately the layout used on the wire reflects the realities of the real
register set: the standard Cortex-M regs plus the VFP ones. Theoretically
it's possible someone might like to do away with the VFP pseudo regs and
make the format be 32 single precision registers; but if you did, it would
need a fair bit more GDB work for no actual practical benefit.

So I expect the format I've proposed is the natural format everyone would
want to use.

> 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.

Because they run on the host, something that's easier for them to do is
supply their own target description XML over the wire. It's also easier to
just update and run a new version if they need to. In contrast, eCos's
stub is programmed into target flash and run on the target, and as you
know, many of the Cortex-M implementations out there have very limited
memory - bytes count. Using a GDB stub on the target is hard enough,
without increasing the footprint further with that. So speaking selfishly,
it doesn't matter so much about OpenOCD or J-link compared to things which
are programmed directly onto hardware, which are harder to change. They
won't care as much about the format as it's easier for them to adapt.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
  **   Visit us at NEW:UK - the UK Embedded & Electronics Exhibition  **
  **   ARM Partner Pavilion/Stand #114. 18-19 April. Birmingham NEC   **
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


  reply	other threads:[~2012-04-19 16:59 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
2012-04-19 17:30       ` Jonathan Larmour [this message]
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=4F90444C.5030505@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gnu.terry@gmail.com \
    --cc=ilijak@siva.com.mk \
    --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