From: John Gilmore <gnu@toad.com>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: RFC: free pending blocks
Date: Thu, 29 Nov 2012 01:24:00 -0000 [thread overview]
Message-ID: <201211290124.qAT1OQ2N007037@new.toad.com> (raw)
In-Reply-To: <87vccp8lm8.fsf@fleche.redhat.com>
That's a nice improvement.
Would it perhaps be better to just allocate these pending blocks
on their own obstack, so they can all be freed at once without doing
a lot of pointer walking?
(Or, deallocate them as they are walked to make the blockvector, to
improve cache locality, rather than in a separate pointer chain walk.)
I don't know how many such blocks are likely to exist in typical
programs, but I suspect there could be thousands.
John
next prev parent reply other threads:[~2012-11-29 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 21:26 Tom Tromey
2012-11-29 1:24 ` John Gilmore [this message]
2012-11-29 14:30 ` Tom Tromey
2012-11-29 14:22 ` Tom Tromey
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=201211290124.qAT1OQ2N007037@new.toad.com \
--to=gnu@toad.com \
--cc=gdb@sourceware.org \
--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