This is the mail archive of the gcc@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: Optimization of conditional access to globals: thread-unsafe?

From: Tomash Brechko <tomash dot brechko at gmail dot com>
To: Eric Botcazou <ebotcazou at libertysurf dot fr>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 29 Oct 2007 11:22:21 +0300
Subject: Re: Optimization of conditional access to globals: thread-unsafe?
References: <20071028.183730.37179404.davem@davemloft.net> <20071029074313.GA4915@moonlight.home> <20071029080307.GB4915@moonlight.home> <200710290912.09560.ebotcazou@libertysurf.fr>

On Mon, Oct 29, 2007 at 09:12:09 +0100, Eric Botcazou wrote:
> Define "final value".

The value that will be seen by other threads after they synchronize
memory (with pthread_mutex_lock(), for instance).


-- 
   Tomash Brechko

Follow-Ups:
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Eric Botcazou

References:
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: David Miller
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Tomash Brechko
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Tomash Brechko
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Eric Botcazou

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