From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13771 invoked by alias); 19 Jun 2007 15:30:34 -0000 Received: (qmail 13701 invoked by uid 48); 19 Jun 2007 15:30:25 -0000 Date: Tue, 19 Jun 2007 15:30:00 -0000 Message-ID: <20070619153025.13700.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288 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: 2007-06/txt/msg01577.txt.bz2 ------- Comment #8 from burnus at gcc dot gnu dot org 2007-06-19 15:30 ------- Bob, > Can you please tell me why the compiler flags "tauaero.f:1517" while > the problem seems to be associated with the data statement at line > 1601? The line number shown when an internal compiler error occurs is often not reliably; often something goes wrong at one place, but this is only triggered when the compiler is at a completely different place. I found the line using other compilers; but also the brand-new error message of the gfortran 4.3 compiler shows now: tauaero.f:1601.17: data wlbaer/0.,0./ 1 tauaero.f:1587.21: & wlbaer(2)=0., 2 Error: 'wlbaer' at (1) already is initialized at (2) Thus either "=0." in line 1587 or "data wlbaer/0.,0./" needs to be removed. > I have tried your suggestion (commenting out the data > statement), but the code does not appear to work correctly with this > modification. I miss a good test case. If you have one, I'm really interested. However, I found some divergence in the output compared with other compilers, see PR 32404. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236