From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 6/8] Types GC [the GC itself]
Date: Tue, 09 Jun 2009 20:25:00 -0000 [thread overview]
Message-ID: <m3tz2pi27z.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090525080323.GF13323@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon\, 25 May 2009 10\:03\:23 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> run the mark-and-sweep garbage collector. Just without the next
Jan> patch 7/8 there will be crashes as not all the GDB reclaimable
Jan> types will be properly being marked.
This seems reasonable to me. I have a couple nits though.
Jan> +/* A traverse callback for type_group_link_table which removes any
Jan> + type_group_link whose reference count is now zero (unused link). */
Why bother with reference counts?
Jan> +void
Jan> +exp_types_mark_used (struct expression *exp)
Jan> +{
Jan> + exp_iterate (exp, exp_types_mark_used_iter, NULL, NULL);
Jan> +}
This is not called anywhere with this patch. I didn't check later
patches yet, so just ignore this if it is called later.
Tom
prev parent reply other threads:[~2009-06-09 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 8:03 Jan Kratochvil
2009-05-25 20:56 ` Eli Zaretskii
2009-05-26 18:15 ` Jan Kratochvil
2009-05-26 19:38 ` Eli Zaretskii
2009-06-09 20:25 ` 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=m3tz2pi27z.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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