From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14097 invoked by alias); 28 May 2011 11:28:37 -0000 Received: (qmail 14084 invoked by uid 22791); 28 May 2011 11:28:36 -0000 X-SWARE-Spam-Status: No, hits=-2.7 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; Sat, 28 May 2011 11:28:23 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49103] [4.6/4.7 Regression] local variables exchange values / wrong code with -O3 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.1 X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sat, 28 May 2011 11:29:00 -0000 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-05/txt/msg02811.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49103 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #9 from Tobias Burnus 2011-05-28 11:27:55 UTC --- (In reply to comment #8) > I am a little bit confused by the answer: My understanding is: It's a middle-end bug, which got exposed by Rev. 169083, but which can occur also with other C, C++ or Fortran code. A proper fix will presumably 4.7 only as it should be rather invasive; cf. Michael's patch at http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02029.html which also should fix PR 39604? For 4.6 one probably needs a different, less invasive patch.