From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17270 invoked by alias); 16 Jul 2005 17:53:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 17205 invoked by uid 22791); 16 Jul 2005 17:52:55 -0000 Received: from h-68-164-203-246.nycmny83.covad.net (HELO dberlin.org) (68.164.203.246) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 16 Jul 2005 17:52:55 +0000 Received: from [127.0.0.1] (HELO localhost) by dberlin.org (CommuniGate Pro SMTP 4.3.4) with ESMTP id 8208802; Sat, 16 Jul 2005 13:52:53 -0400 Subject: Re: volatile semantics From: Daniel Berlin To: Andrew Haley Cc: "D. Hugh Redelmeier" , gcc@gcc.gnu.org, Nathan Sidwell , Dale Johannesen , Mike Stump In-Reply-To: <17113.17689.558864.411876@zapata.pink> References: <851D2CB0-93DF-4C49-A6A8-8895DB1A08F9@apple.com> <42778D99.7070904@codesourcery.com> <17113.17689.558864.411876@zapata.pink> Content-Type: text/plain Date: Sat, 16 Jul 2005 17:53:00 -0000 Message-Id: <1121536373.29893.10.camel@linux.site> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00670.txt.bz2 > In other words, we're asked to agree that the type of an object > changes depending on how it is accessed. > For the benefit of readers, only the first sentence of this para is > the language of the standard; the rest isn't. > > That an object referred to through a volatile pointer must > "temporarily" be treated as though it were declared volatile is the > crux of this argument. Again, you could say the same about const, restrict, or any other qualifier then, making them more or less useless as qualifiers.