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: Eric Botcazou <ebotcazou at libertysurf dot fr>
To: Tomash Brechko <tomash dot brechko at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 29 Oct 2007 09:50:16 +0100
Subject: Re: Optimization of conditional access to globals: thread-unsafe?
References: <20071028.183730.37179404.davem@davemloft.net> <20071029084210.GE4915@moonlight.home> <20071029084436.GF4915@moonlight.home>

> And because your next question will be "how the compiler will know the
> corresponding mutex", the answer is: it can't, that's why "opaque
> function" rules come to play.

Right, so please define more or less formally what the "final value" is from 
the viewpoint of the current thread, this is the crux of the matter.

-- 
Eric Botcazou

Follow-Ups:
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Tomash Brechko

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

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