From: Tom Tromey <tromey@redhat.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: Fri, 27 Apr 2012 15:55:00 -0000 [thread overview]
Message-ID: <87vckl41dt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F99D8A5.8050702@eCosCentric.com> (Jonathan Larmour's message of "Fri, 27 Apr 2012 00:22:13 +0100")
>>>>> "Jifl" == Jonathan Larmour <jifl@eCosCentric.com> writes:
Jifl> I assume you mean having it in the stub in a pre-compressed form; in which
Jifl> case yes, that helps[1].
Yeah.
Jifl> But if GDB could handle compressed target descriptions, that would
Jifl> be useful. Perhaps the stub could use a different $qSupported
Jifl> response to indicate its compressed, or perhaps GDB could
Jifl> recognise magic numbers at the start of a $qXfer:features:read
Jifl> response and pass to zlib. (e.g. gzip is always 0x1f,0x8b).
Yeah, I think it would be a reasonable addition.
Tom
next prev parent reply other threads:[~2012-04-27 15:54 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
2012-04-26 23:40 ` Jonathan Larmour
2012-04-27 15:55 ` Tom Tromey [this message]
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=87vckl41dt.fsf@fleche.redhat.com \
--to=tromey@redhat.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