From: Jonathan Larmour <jifl@eCosCentric.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Terry Guo <terry.guo@arm.com>, 'Pedro Alves' <palves@redhat.com>,
Yao Qi <yao@codesourcery.com>,
gdb-patches@sourceware.org, tromey@redhat.com,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Joey Ye <Joey.Ye@arm.com>
Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub
Date: Wed, 13 Jun 2012 13:47:00 -0000 [thread overview]
Message-ID: <4FD899D8.7080903@eCosCentric.com> (raw)
In-Reply-To: <201206131312.q5DDCUfK028160@d06av02.portsmouth.uk.ibm.com>
On 13/06/12 14:12, Ulrich Weigand wrote:
> Terry Guo wrote:
>
>> Yes, we need to consider xi:includes which means we have to involve a
>> global state.
>
> Not necessarily; the way I had intended my suggestion to work was that
> GDB always adds ".gz" (or some other suffix if we actually are not
> compatible with the .gz file format) to *every* file it fetches, not
> just to the initial target.xml, but also to other files fetched via
> xi:include statements ...
>
> If the compressed version of the file is not available, GDB would
> then fall back to the original file name (on a file-by-file basis).
I agree.
This also means that the target can choose whether to return any file as
compressed or not, rather than having to have everything compressed from
then on, even if some XML files might take up more space compressed than
uncompressed, or might need to be generated - but not all files. It's
getting a bit hypothetical at this point, it's true, but not unreasonably so.
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.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next prev parent reply other threads:[~2012-06-13 13:47 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 [this message]
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
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=4FD899D8.7080903@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=Joey.Ye@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=terry.guo@arm.com \
--cc=tromey@redhat.com \
--cc=uweigand@de.ibm.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