From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/PATCH] PR/9711: quadratic slowdown for deep stack traces
Date: Thu, 03 Sep 2009 20:27:00 -0000 [thread overview]
Message-ID: <m3y6ovepvv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090903183658.GJ4343@adacore.com> (Joel Brobecker's message of "Thu, 3 Sep 2009 11:36:58 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> My only complaint with this patch is that it introduces a slight
Joel> confusion: The current code says we "cache" all the frames when it
Joel> talks about the frame chain corresponding to the backtrace. My patch
Joel> introduces a "frame cache". I'm OK with renaming my cache into
Joel> something else, but couldn't find a better name.
Joel> I'll also attach a couple of files that move the new frame cache
Joel> to a different file (frame-cache.c). I think it's cleaner, but the issue
Joel> is that we cannot access the frame ID from the frame since struct frame
Joel> is opaque.
I actually prefer the version where the code is in frame.c, because I
think of this cache as an implementation detail of the frame code.
But, 6 of one, I'd support either version.
Joel> Any suggestion of a new name for my frame_cache?
The word "memoize" came to mind.
Joel> Any objection to me checking in this patch?
Not from me, it seems like a good idea.
Tom
next prev parent reply other threads:[~2009-09-03 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 18:37 Joel Brobecker
2009-09-03 20:27 ` Tom Tromey [this message]
2009-09-07 7:30 ` Doug Evans
2009-09-07 20:33 ` Joel Brobecker
2009-09-07 20:48 ` Doug Evans
2009-09-07 20:57 ` Pedro Alves
2009-09-07 22:00 ` Joel Brobecker
2009-09-07 22:21 ` Pedro Alves
2009-09-07 23:12 ` Joel Brobecker
2009-09-08 0:06 ` Joel Brobecker
2009-09-09 17:39 ` Joel Brobecker
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=m3y6ovepvv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.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