This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
RE: Garbage collector problem ???
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Subject: RE: Garbage collector problem ???
- From: Alexandre Petit-Bianco <apbianco at cygnus dot com>
- Date: Fri, 19 Jan 2001 10:34:15 -0800 (PST)
- Cc: "'balrog at amena dot com'" <balrog at amena dot com>, <java-discuss at sources dot redhat dot com>
- References: <140D21516EC2D3119EE700902787664401E3A84E@hplex1.hpl.hp.com>
- Reply-To: apbianco at cygnus dot com
Boehm, Hans writes:
> That would be safe for Java arrays if we knew that the compiler
> always kept a pointer to the array itself while the array could
> still be dereferenced.
You mean (1) always address an array element with an arithmetic that
starts from the pointer to the array object? Or (2) always keep a
pointer to the array object around, while addressing on of its
element?
The current front-end does (1), though this can be optimized in weird
ways. I'm not sure (2) is guaranteed, because of optimizations.
> I believe currently the front end ensures that, but not in a way
> that ensures the back end will preserve the property.
I'll see if some hints can be passed to the middle and back-end.
./A