From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25853 invoked by alias); 2 Feb 2011 09:35:40 -0000 Received: (qmail 25794 invoked by uid 22791); 2 Feb 2011 09:35:39 -0000 X-SWARE-Spam-Status: No, hits=-2.6 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; Wed, 02 Feb 2011 09:35:35 +0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47574] internal compiler error: in build2_stat, at tree.c:3795 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: dominiq at lps dot ens.fr 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: 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: Wed, 02 Feb 2011 09:35: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-02/txt/msg00250.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47574 --- Comment #8 from Dominique d'Humieres 2011-02-02 09:35:31 UTC --- (In reply to comment #6) > I have used gdb for minimally, but what is its use here? I cannot create an > executable if I do not reduce the optimization level. What do you suggest? I suggest to run gdb on f951 to see the path leading to the error exch2_uv_agrid_3d_rl.f:293:0: internal compiler error: in build2_stat, at tree.c:3795 gfortran is located in /some_path/bin. You'll find f951 in /some_path/libexec/gcc/platform/version/ (gdb /opt/gcc/gcc4.6w/libexec/gcc/x86_64-apple-darwin10.6.0/4.6.0/f951 for me). Set a breakpoint to fancy_abort, run the code and do a backtrace. (In reply to comment #7) > What makes the problem go away is commenting out line 949. There is no line 949 in attachment 23201. The goal is to reduce the file to the "minimal" size reproducing the ICE. CALL and COMMON have triggered bugs in the past, hence my question (note that in the attachment 23201 there are only two COMMONs: /EEPARAMS_L/ and /EEPARAMS_I/).