From: Tom Tromey <tromey@redhat.com>
To: Chris Moller <cmoller@redhat.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [tools-team] 11874 Vector pretty-printer chokes on bit-vectors
Date: Mon, 16 Aug 2010 18:17:00 -0000 [thread overview]
Message-ID: <m3ocd2mnho.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C695337.5030908@redhat.com> (Chris Moller's message of "Mon, 16 Aug 2010 11:03:19 -0400")
>>>>> "Chris" == Chris Moller <cmoller@redhat.com> writes:
Chris> If it's a sparse vector, yeah, you're right. But it's probably more
Chris> trouble than it's worth to figure that out and do different things
Chris> depending, and, on average, it probably dumps more chares to print the
Chris> indices of the '1's than to print all of the bits.
Sounds reasonable.
For future reference, this is the wrong list for libstdc++ patches.
I will forward this and apply it to gcc.
Tom
prev parent reply other threads:[~2010-08-16 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C653282.4050204@redhat.com>
[not found] ` <m38w4a1qje.fsf@fleche.redhat.com>
[not found] ` <4C659A95.1060207@redhat.com>
[not found] ` <m38w4aw4z2.fsf@fleche.redhat.com>
2010-08-16 15:03 ` Chris Moller
2010-08-16 18:17 ` Tom Tromey [this message]
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=m3ocd2mnho.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cmoller@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).