This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Add support for VFP d16 layout for Cortex-M4
- From: Tom Tromey <tromey at redhat dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org, Ilija Kocho <ilijak at siva dot com dot mk>, Terry Guo <terry dot guo at arm dot com>
- Date: Thu, 26 Apr 2012 13:35:31 -0600
- Subject: Re: [patch] Add support for VFP d16 layout for Cortex-M4
- References: <4F902B4E.9070704@eCosCentric.com> <4F91593B.4020309@redhat.com> <4F95FA8C.7000509@eCosCentric.com>
>>>>> "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