This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: status of gcj's boehm collector?
- From: Tom Tromey <tromey at redhat dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Adam Megacz'" <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
- Date: 05 Dec 2001 14:12:19 -0700
- Subject: Re: status of gcj's boehm collector?
- References: <40700B4C02ABD5119F000090278766443BEDD0@hplex1.hpl.hp.com>
- Reply-to: tromey at redhat dot com
>>>>> "Hans" == Boehm, Hans <hans_boehm@hp.com> writes:
Hans> 1) Use a software write barrier. Insert instructions to keep
Hans> track of heap writes. This is what JVMs with generational
Hans> collectors generally do. It's not free. It would be hard to do
Hans> in gcj because the C++ code would have to play by the rules.
Jon Olson added write barrier support to gcc in the back end. If we
used this approach we could add it to both g++ and gcj. There might
be some odd special cases, but it is doable.
This sounds like something that would get put on a wish list and never
done, unless some volunteer were really motivated. My question to you
is whether it would be worthwhile in the context of your GC.
Tom