From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 950 invoked by alias); 16 Jul 2005 22:57:48 -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 940 invoked by uid 22791); 16 Jul 2005 22:57:44 -0000 Received: from smtp-106-saturday.nerim.net (HELO kraid.nerim.net) (62.4.16.106) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 16 Jul 2005 22:57:44 +0000 Received: from uniton.integrable-solutions.net (gdr.net1.nerim.net [62.212.99.186]) by kraid.nerim.net (Postfix) with ESMTP id E635D40E1E; Sun, 17 Jul 2005 00:57:40 +0200 (CEST) Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j6GMuppI027675; Sun, 17 Jul 2005 00:56:51 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.10/8.12.10/Submit) id j6GMupfu027672; Sun, 17 Jul 2005 00:56:51 +0200 To: "D. Hugh Redelmeier" Cc: Daniel Berlin , gcc@gcc.gnu.org, Nathan Sidwell , Dale Johannesen , Mike Stump Subject: Re: volatile semantics References: <851D2CB0-93DF-4C49-A6A8-8895DB1A08F9@apple.com> <42778D99.7070904@codesourcery.com> <1121532997.29893.6.camel@linux.site> <1121548071.6761.7.camel@linux.site> From: Gabriel Dos Reis In-Reply-To: Date: Sat, 16 Jul 2005 22:57:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-07/txt/msg00694.txt.bz2 "D. Hugh Redelmeier" writes: | | From: Gabriel Dos Reis | | | The way I see it is that people who designed and wrote the standard | | offer their view and interpretation of of they wrote and some people | | are determined to offer a different interpretation so that they can | | claim they are well-founded to apply their transformations. | | I don't know exactly what you are referring to here. That's OK, I | think. yes :-) | The standard should stand alone. It should be able to be interpreted | without "insider knowledge". fully agreed. | The standard is quite complicated and intricate. It helps to already | know it when trying to read it. (On the other hand, that same | phenomenon makes it hard for the authors to see its ambiguities.) again agreed. | Generations have worked on improving the standards. Not all of the | changes were made by people who understood what went before. no displute there. | Having said all that, I think that the standard gives no authority to | do the optimization that GCC4 is doing to the code sample I gave. I | included Henry's carefully justified-by-scripture argument. If anyone | disagrees, PLEASE give a careful argument why, siting the Standard. | | If you wish to answer other questions about the standard, I recommend | that the first step would be to read the standard. Arguing by opinion | isn't getting us too far. Again agreed. | PS: thanks for not just ignoring my report. well, feedbacks are always welcome and it would not help us if we did "just ignore" them. After many exchanges via private mails and looking at the various reports related to this issue, it has become clear to me that the interpretations offered to justify why GCC is behaving the way it does seem to go beyond what can be inferred. -- Gaby