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: Heads-up: volatile and C++

From: Jason Merrill <jason at redhat dot com>
To: Robert Dewar <dewar at adacore dot com>
Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, "Michael N. Moran" <mike at mnmoran dot org>, gcc at gcc dot gnu dot org
Date: Thu, 14 Apr 2005 23:33:48 +0200
Subject: Re: Heads-up: volatile and C++
References: <xypfyxtipo1.fsf@miranda.boston.redhat.com><425E7A55.8050105@mnmoran.org><xypaco1icyz.fsf@miranda.boston.redhat.com><425ECB38.9050708@adacore.com><m3ekddnkcw.fsf@uniton.integrable-solutions.net><425ED6F0.30405@adacore.com>

On Thu, 14 Apr 2005 15:47:44 -0500, Robert Dewar <dewar@adacore.com> wrote:
> [Ada standard]

Yep, sounds a lot like C/C++: volatile reads and writes are required to
have sequential ordering relative to each other, but (outside the current
thread) they are not ordered relative to non-volatile reads and writes.

Jason

Follow-Ups:
- Re: Heads-up: volatile and C++
  - From: Paul Koning
- Re: Heads-up: volatile and C++
  - From: Duncan Sands

References:
- Heads-up: volatile and C++
  - From: Jason Merrill
- Re: Heads-up: volatile and C++
  - From: Michael N. Moran
- Re: Heads-up: volatile and C++
  - From: Jason Merrill
- Re: Heads-up: volatile and C++
  - From: Robert Dewar
- Re: Heads-up: volatile and C++
  - From: Gabriel Dos Reis
- Re: Heads-up: volatile and C++
  - From: Robert Dewar

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