This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GC failure w/ THREAD_LOCAL_ALLOC ?

From: Tom Tromey <tromey at redhat dot com>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: "Boehm, Hans" <hans_boehm at hp dot com>, "'Michael Smith'" <msmith at spinnakernet dot com>, "'java at gcc dot gnu dot org'" <java at gcc dot gnu dot org>, "'Jeff Sturm'" <jsturm at one-point dot com>
Date: 26 Mar 2002 17:45:49 -0700
Subject: Re: GC failure w/ THREAD_LOCAL_ALLOC ?
References: <40700B4C02ABD5119F000090278766443BF0C9@hplex1.hpl.hp.com> <87sn6mx4b9.fsf@creche.redhat.com> <3CA10AAC.4030507@waitaki.otago.ac.nz>
Reply-to: tromey at redhat dot com

>>>>> "Bryce" == Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:

Bryce> Well, I noticed that it is much more likely to happen when the
Bryce> machine is busy with other tasks. If the machine is otherwise
Bryce> idle, the problem doesn't seem to occur.

I tried a lot of things, including rebuilding gcc while running it,
but can't cause it to fail on x86.  On the alpha I can make it fail
pretty easily, as it turns out, by using different parameters.  `50
50' makes it fail there.

BTW I submitted a high-priority PR for this so we can track it.
I found I was losing track of everything going on, so I've started
entering PRs for anything I think we need to fix for 3.1.

Tom

Follow-Ups:
- Re: GC failure w/ THREAD_LOCAL_ALLOC ?
  - From: Bryce McKinlay

References:
- RE: GC failure w/ THREAD_LOCAL_ALLOC ?
  - From: Boehm, Hans
- Re: GC failure w/ THREAD_LOCAL_ALLOC ?
  - From: Tom Tromey
- Re: GC failure w/ THREAD_LOCAL_ALLOC ?
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]