This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: GC failure w/ THREAD_LOCAL_ALLOC ?
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- To: "'Michael Smith'" <msmith at spinnakernet dot com>, "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'tromey at redhat dot com'" <tromey at redhat dot com>, "'Jeff Sturm '" <jsturm at one-point dot com>, "''Bryce McKinlay ' '" <bryce at waitaki dot otago dot ac dot nz>, "'java at gcc dot gnu dot org'" <java at gcc dot gnu dot org>
- Date: Mon, 1 Apr 2002 08:53:27 -0800
- Subject: RE: GC failure w/ THREAD_LOCAL_ALLOC ?
> -----Original Message-----
> From: Michael Smith [mailto:msmith@spinnakernet.com]
> With the rest of the changes applied, I can no longer replicate the
> problem using GCTest.
>
Great! Thanks for checking that.
>
> Do you recommend running without GC_IGNORE_GCJ_INFO now that
> this fix is in?
>
Yes, I would no longer set the environment variable. For at least 9 out of
10 applications it won't matter. The relative speed is probably platform
dependent. But every once in a while you may find one that introduces
enough misidentified pointers to cause appreciable leakage. (In my
experience, this tends to be fairly testable, i.e. it's usually more a
property of the application than the input, but still ...) In the absence
of known bugs, I would always use the available type information.
Hans