This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Garbage Collector Issues on Win98/gcj 4.02
- From: Tom Tromey <tromey at redhat dot com>
- To: Mohan Embar <gnustuff at thisiscool dot com>
- Cc: java at gcc dot gnu dot org
- Date: 24 May 2006 07:09:14 -0600
- Subject: Re: Garbage Collector Issues on Win98/gcj 4.02
- References: <4WY1TVPD9YW952YDC65QKNJ09VUSNJF.4473bec8@d9300>
- Reply-to: tromey at redhat dot com
>>>>> "Mohan" == Mohan Embar <gnustuff@thisiscool.com> writes:
Mohan> What are the consequences of these being born with state==JV_STATE_DONE?
Mohan> Does this mean they shouldn't be collected?
Nope. The state is used primarily while linking the class at
runtime. Linking is a multi-step process and different steps are
done in different situations. The states are explained briefly in
Class.h; link.cc:wait_for_state() is how a transition to a particular
state is requested.
Array classes are created in state JV_STATE_DONE only because no more
linking is required after they are created.
Mohan> I'm not quite clear on what you're proposing here. Are you saying that
Mohan> it would be better to:
Mohan> - conditionalize this with "if (engine)"?
This one.
Mohan> - add a new execution engine for arrays?
This is my second choice. The execution engine for a class is used in
a number of places, I think I'd prefer that arrays trigger SEGVs in
those places, since at the moment that would mean we've hit a serious
bug.
Tom