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: Using __kuser_cmpxchg

From: Andrew Haley <aph-gcc at littlepinkcloud dot COM>
To: Nicolas Pitre <nico at cam dot org>
Cc: Paul Brook <paul at codesourcery dot com>, java at gcc dot gnu dot org, linux-arm-kernel at lists dot arm dot linux dot org dot uk
Date: Thu, 15 Nov 2007 20:59:01 +0000
Subject: Re: Using __kuser_cmpxchg
References: <200711151759.lAFHxKa4027497@devserv.devel.redhat.com> <alpine.LFD.0.9999.0711151326510.21255@xanadu.home> <18236.39235.500965.810488@zebedee.pink> <alpine.LFD.0.9999.0711151443300.21255@xanadu.home>

Nicolas Pitre writes:
 > On Thu, 15 Nov 2007, Andrew Haley wrote:
 > 
 > In the mean time you can work around it by using a mutex around the 
 > thread state modification instead of using cmpxchg on it.  Or if your 
 > platform is ARMv6 or higher then you won't get those spurious false 
 > negatives.

Ah, OK, that's interesting: it sounds like you understand under what
circumstances it may fail "spuriously".  What are these?

Andrew.

Follow-Ups:
- Re: Using __kuser_cmpxchg
  - From: Nicolas Pitre

References:
- Re: Using __kuser_cmpxchg
  - From: Nicolas Pitre
- Re: Using __kuser_cmpxchg
  - From: Andrew Haley
- Re: Using __kuser_cmpxchg
  - From: Nicolas Pitre

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