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 22:30:20 +0100
Subject: Re: Optimization of conditional access to globals: thread-unsafe?
References: <20071028.183730.37179404.davem@davemloft.net> <200710290950.16593.ebotcazou@libertysurf.fr> <20071029085525.GG4915@moonlight.home>

> But shouldn't we formally define "define" first? :)

Note that I wrote "more or less formally".  The definition of "volatile" in 
the ISO C standard falls into this category and I'd personally trust it more 
than whatever -fno-speculative-store option.

See gcc/gthr-posix.h for a proper use of "volatile" for a shared access.

-- 
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: Eric Botcazou
- 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]