From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: palves@redhat.com (Pedro Alves), terry.guo@arm.com (Terry Guo),
jifl@ecoscentric.com ('Jonathan Larmour'),
yao@codesourcery.com (Yao Qi),
gdb-patches@sourceware.org, tromey@redhat.com,
Richard.Earnshaw@arm.com (Richard Earnshaw)
Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub
Date: Thu, 14 Jun 2012 14:58:00 -0000 [thread overview]
Message-ID: <201206141458.q5EEwCRJ008704@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20120614135412.GK18729@adacore.com> from "Joel Brobecker" at Jun 14, 2012 06:54:12 AM
Joel Brobecker wrote:
> > In that perspective, something like the
> > 'try qXfer:features:zread:target.xml first, then
> > qXfer:features:read:target.xml, etc.' alternative sounded attractive.
> > Or should we not bother?
>
> Sounds more attractive indeed.
The reason for suggesting just a different filename was simply
that this can use the existing infrastructure without much change.
On the other hand, :zread not only introduces a new packet type,
but in fact a completely new operation class for qXfer packets.
If this is going to be used just for the one special case, I'm
not sure it is worthwhile to bother with this. If however we
feel that :zread could become useful for other situations
(e.g. other qXfer objects beside qXfer:features), then I certainly
don't object to adding it ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-06-14 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 7:31 Terry Guo
2012-06-11 14:43 ` Jonathan Larmour
2012-06-12 9:37 ` Terry Guo
2012-06-12 12:44 ` Yao Qi
2012-06-12 12:57 ` Ulrich Weigand
2012-06-12 16:24 ` Jonathan Larmour
2012-06-13 1:58 ` Terry Guo
2012-06-13 13:42 ` Jonathan Larmour
2012-06-14 0:53 ` Terry Guo
2012-06-13 11:57 ` Terry Guo
2012-06-13 12:26 ` Pedro Alves
2012-06-13 12:51 ` Terry Guo
2012-06-13 13:12 ` Ulrich Weigand
2012-06-13 13:47 ` Jonathan Larmour
2012-06-14 1:11 ` Terry Guo
2012-06-14 10:14 ` Pedro Alves
2012-06-14 13:54 ` Joel Brobecker
2012-06-14 14:58 ` Ulrich Weigand [this message]
2012-06-14 15:38 ` Jonathan Larmour
2012-06-19 7:40 ` Terry Guo
2012-06-22 17:19 ` Jonathan Larmour
2012-06-26 2:39 ` Terry Guo
2012-06-26 3:24 ` Terry Guo
2012-06-26 11:58 ` Jonathan Larmour
2012-06-27 3:42 ` Terry Guo
2012-06-27 21:25 ` 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=201206141458.q5EEwCRJ008704@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jifl@ecoscentric.com \
--cc=palves@redhat.com \
--cc=terry.guo@arm.com \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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