This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [committed] Change default for enable_hash_synchronization_default on PA-RISC

From: Andreas Tobler <toa at pop dot agri dot ch>
To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
Date: Fri, 16 Jun 2006 00:12:39 +0200
Subject: Re: [committed] Change default for enable_hash_synchronization_default on PA-RISC
References: <200606140151.k5E1puKk005475@hiauly1.hia.nrc.ca>

John David Anglin wrote:

I've noticed that we get occassional failures of process intensive
tests in the libjava testsuite (e.g., Process_3).  Carlos O'Donell
indicated that hashing locks might be unsafe because of the special
way locks are handled in parisc-linux.  I've also seen a few failures
in the libjava suite on hpux.  So, I've decided that it would be
better to be conservative in this regard.

What failures exactly on hpux? I did not see anything unusal on hpux since we put in the port.

Andreas

Follow-Ups:
- Re: [committed] Change default for enable_hash_synchronization_default
  - From: John David Anglin

References:
- [committed] Change default for enable_hash_synchronization_default on PA-RISC
  - From: John David Anglin

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