From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-117309-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20395 invoked by alias); 16 Jul 2005 19:05:27 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 20382 invoked by uid 22791); 16 Jul 2005 19:05:23 -0000
Received: from mail-out3.apple.com (HELO mail-out3.apple.com) (17.254.13.22)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 16 Jul 2005 19:05:23 +0000
Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204])
	by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id j6GJ5Lau007401
	for <gcc@gcc.gnu.org>; Sat, 16 Jul 2005 12:05:21 -0700 (PDT)
Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.3.17) with ESMTP id <T722bf1875e118064cc37c@mailgate2.apple.com>;
 Sat, 16 Jul 2005 12:05:20 -0700
Received: from [17.219.205.151] ([17.219.205.151])
	by relay2.apple.com (8.12.11/8.12.11) with ESMTP id j6GJ5Ie9010914;
	Sat, 16 Jul 2005 12:05:18 -0700 (PDT)
In-Reply-To: <17113.17689.558864.411876@zapata.pink>
References: <851D2CB0-93DF-4C49-A6A8-8895DB1A08F9@apple.com> <42778D99.7070904@codesourcery.com> <b0f8ff9938df57bbfda0ec3aea4fc02b@apple.com> <Pine.LNX.4.61.0507161250120.1478@redshift.mimosa.com> <17113.17689.558864.411876@zapata.pink>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <a315399723d359b46360b94cbdcb1af4@apple.com>
Content-Transfer-Encoding: 7bit
Cc: "D. Hugh Redelmeier" <hugh@mimosa.com>, gcc@gcc.gnu.org,
        Dale Johannesen <dalej@apple.com>,
        Nathan Sidwell <nathan@codesourcery.com>, Mike Stump <mrs@apple.com>
From: Dale Johannesen <dalej@apple.com>
Subject: Re: volatile semantics
Date: Sat, 16 Jul 2005 19:05:00 -0000
To: Andrew Haley <aph@redhat.com>
X-SW-Source: 2005-07/txt/msg00673.txt.bz2


On Jul 16, 2005, at 10:34 AM, Andrew Haley wrote:

>> 6.3.2.1:  when an object is said to have a particular type, the type 
>> is
>> specified by the lvalue used to designate the object.

I don't have a standard here, but I will point out that IF this 
sentence is
interpreted to mean

>  the type of an object
> changes depending on how it is accessed.

this also makes nonsense of gcc's implementation of type-based aliasing
rules.

   *((int *)&x) = 3

would then be valid whatever the type of x.