From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15852 invoked by alias); 12 Sep 2011 09:08:29 -0000 Received: (qmail 15842 invoked by uid 22791); 12 Sep 2011 09:08:28 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Sep 2011 09:08:11 +0000 From: "abramobagnara at tin dot it" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50364] New: Volatile miscompilation Date: Mon, 12 Sep 2011 09:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: abramobagnara at tin dot it X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg00811.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50364 Bug #: 50364 Summary: Volatile miscompilation Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: abramobagnara@tin.it $ cat p.cc volatile int a, b; void f() { b = 1 + (a = 0); } $ g++ -O2 -S p.cc $ cat p.s .file "p.cc" .text .p2align 4,,15 .globl _Z1fv .type _Z1fv, @function _Z1fv: .LFB0: .cfi_startproc movl $0, a movl $1, b ret .cfi_endproc ... As the typescript above shows, the conversion between lvalue (a = 0) and relative rvalue does not generate a volatile read memory access unlike what I think that standard mandates.