From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28051 invoked by alias); 21 Sep 2011 16:58:46 -0000 Received: (qmail 28036 invoked by uid 22791); 21 Sep 2011 16:58:45 -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; Wed, 21 Sep 2011 16:58:32 +0000 From: "janus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50410] [4.6/4.7 Regression] ICE in record_reference Date: Wed, 21 Sep 2011 19:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus 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: --- X-Bugzilla-Changed-Fields: Keywords 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 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/msg01475.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code CC| |janus at gcc dot gnu.org --- Comment #5 from janus at gcc dot gnu.org 2011-09-21 16:58:29 UTC --- (In reply to comment #4) > The code is invalid and so gfortran can do anything that it > wishes, including segfault. Well, no. An ICE on invalid code may not be as bad as an ICE on valid code, but it's still a bug. gfortran should give a meaningful error message.