From: Tom Tromey <tromey@redhat.com>
To: Andrew Gontarek <andrewg@cray.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 12705: Extremely poor performance when printing large arrays
Date: Fri, 29 Apr 2011 19:15:00 -0000 [thread overview]
Message-ID: <m3oc3odg3b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m339l1dkfw.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 29 Apr 2011 11:41:23 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I am running this through our tester, and if it works ok I am going to
Tom> check it in. It looks safe enough for 7.3 as well.
I am checking it in now.
Tom
prev parent reply other threads:[~2011-04-29 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:26 Andrew Gontarek
2011-04-29 17:41 ` Tom Tromey
2011-04-29 19:15 ` 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=m3oc3odg3b.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andrewg@cray.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