From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19350 invoked by alias); 17 May 2010 20:40:27 -0000 Received: (qmail 18693 invoked by uid 48); 17 May 2010 20:40:02 -0000 Date: Mon, 17 May 2010 20:40:00 -0000 Message-ID: <20100517204002.18690.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/44177] gfortran internal data assignment error cause found In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus at gcc dot gnu dot org" 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: 2010-05/txt/msg01859.txt.bz2 ------- Comment #3 from burnus at gcc dot gnu dot org 2010-05-17 20:39 ------- I can confirm the issue with GCC 4.3.4, 4.4.4, and 4.5.0; however, using 4.6 it works. I think the ICE has been fixed by the recent constructor work by Daniel. Thus, one solution is to close the bug as WONTFIX; alternatively, one can check what is needed to fix the PR. Work around is to remove one of the initializations as the variable is initialized twice. Best is to remove the first one as this variant is not standard conform (the DATA statement is). * * * Side note: With 4.6 and "-pedantic" one gets also the expected warnings: real foo(2) /2*0.0/ 1 Warning: Extension: Old-style initialization at (1) data foo /0.0, 0.0/ 1 Warning: Extension: re-initialization of 'foo' at (1) -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|4.4.5 4.5.1 |4.3.4 4.4.0 4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44177