From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-352201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9782 invoked by alias); 2 Apr 2011 10:25:20 -0000
Received: (qmail 9772 invoked by uid 22791); 2 Apr 2011 10:25:19 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,TW_DB,TW_FD
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, 02 Apr 2011 10:25:14 +0000
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48412] [4.7 Regression] CP2K miscompiled due to some Fortran frontend pass
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steven at gcc dot gnu.org
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: CC
Message-ID: <bug-48412-4-gOCL3TLiuL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48412-4@http.gcc.gnu.org/bugzilla/>
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, 02 Apr 2011 10:25:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-04/txt/msg00105.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48412

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #1 from Steven Bosscher <steven at gcc dot gnu.org> 2011-04-02 10:25:12 UTC ---
Joost, perhaps you can narrow it down further by using a debug counter.

You'd have to add a debug counter to dbgcnt.def, say "frontend1" 
Instead of "if (0 ...)", you would add'd do "if (dbg_cnt (frontend1) ...)".

Then compile with -fdbg-cnt=frontend1:N where N is a number, run, and see if
the bug occurs. The trick is to find the greatest value for N where the bug
occurs. This can be done with a binary search, as explained in dbgcnt.def.