Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Smith <psmith@gnu.org>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>,
	gdb	 <gdb@sourceware.org>
Subject: Re: [GDB 7.6/GCC 4.8.0] Slowdown in GDB macro processing for cores?
Date: Tue, 28 May 2013 17:53:00 -0000	[thread overview]
Message-ID: <1369763628.3295.27.camel@pdsdesk> (raw)
In-Reply-To: <CADPb22R78kWcCog5f0OV5sa-F6N08X_p92HSMSX+xy3Wf75q_w@mail.gmail.com>

On Tue, 2013-05-28 at 10:40 -0700, Doug Evans wrote:
> > I'll try the latest Git to see if it makes a difference.
> 
> I'd be curious for before/after data with this patch:
> 
> http://sourceware.org/ml/gdb-patches/2013-05/msg00964.html
> 
> I doubt it fixes everything, or even a lot of it.

I didn't realize that wasn't pushed yet.  In any event I tried the
latest content of Git and then I also tried with the above patch
applied, and there was no appreciable improvement (I didn't do an
in-depth analysis of exactly how many times various functions were
called to see if it improved, but the iterations of the macro continued
to take multiple seconds where they take fractions of a second with
7.5.1).



  reply	other threads:[~2013-05-28 17:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 19:42 Paul Smith
2013-05-17 10:15 ` Pedro Alves
2013-05-22 18:50   ` Paul Smith
2013-05-22 19:20     ` Paul Smith
2013-05-22 20:12       ` Tom Tromey
2013-05-22 20:52         ` Paul Smith
2013-05-22 21:02         ` Paul Smith
2013-05-22 23:14         ` Paul Smith
2013-05-23  2:44           ` Doug Evans
2013-05-23  4:41             ` Paul Smith
2013-05-28 17:11               ` Doug Evans
2013-05-28 17:33                 ` Paul Smith
2013-05-28 17:40                   ` Doug Evans
2013-05-28 17:53                     ` Paul Smith [this message]
2013-05-28 18:03                       ` Doug Evans
2013-05-28 15:25           ` Paul Smith

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=1369763628.3295.27.camel@pdsdesk \
    --to=psmith@gnu.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tromey@redhat.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