From: Tom Tromey <tromey@redhat.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: Pedro Alves <palves@redhat.com>,
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, 26 Apr 2012 20:28:00 -0000 [thread overview]
Message-ID: <87ipgm70cc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F95FA8C.7000509@eCosCentric.com> (Jonathan Larmour's message of "Tue, 24 Apr 2012 01:57:48 +0100")
>>>>> "Jifl" == Jonathan Larmour <jifl@eCosCentric.com> writes:
Jifl> Sorry it's taken me a few days to get back to you, but I've been
Jifl> implementing what's required to send the XML target description
Jifl> support in the eCos stub, so that I could have hard
Jifl> data. Unfortunately it has confirmed my suspicions. Adding code
Jifl> and const data to send back the description for a vanilla Cortex-M
Jifl> profile target has added 1252 bytes to our GDB stub's
Jifl> footprint. If the VFP regs description is added to that, that adds
Jifl> another 931 bytes to give 2183 bytes. That's a big penalty.
Can the XML be compressed?
I don't know. If not, what if it could be?
I'm curious what you use for your stub.
Based on the recent gdb@ threads, it seems like it can't be gdbserver.
Tom
next prev parent reply other threads:[~2012-04-26 19:36 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
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 [this message]
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=87ipgm70cc.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ilijak@siva.com.mk \
--cc=jifl@eCosCentric.com \
--cc=palves@redhat.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