From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-218970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24762 invoked by alias); 22 May 2007 11:18:32 -0000
Received: (qmail 24658 invoked by uid 48); 22 May 2007 11:18:15 -0000
Date: Tue, 22 May 2007 11:18:00 -0000
Subject: [Bug testsuite/32038]  New: gfortran.dg/pr25603.f is invalid code
X-Bugzilla-Reason: CC
Message-ID: <bug-32038-10259@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
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: 2007-05/txt/msg01835.txt.bz2

The testcase gfortran.dg/pr25603.f is invalid code. The following variables are
not initialized:

  lhelpa lhelp lcn lbn lan ldcdy ldcdx lkm ltm lvg lug lvm lum lhvar lzet ldep
  lvdep ltstr lustr lobuk ltavr lsteph lhmix lz0 lelevy lelevx lelev ldkzh
ldkzm
  lq lpstep lpi lwz lvstep lvy lustep lux ltstep lpot lcstep lc

They should be initialized with a value (like 1) if the test is to be run,
otherwise we access array elements out of range. I suggest the following patch
be applied:

Index: gcc/testsuite/gfortran.dg/pr25603.f
===================================================================
--- gcc/testsuite/gfortran.dg/pr25603.f (revision 124903)
+++ gcc/testsuite/gfortran.dg/pr25603.f (working copy)
@@ -44,6 +44,48 @@ C
        call abort
       endif

+      LHELPA = 1
+      LHELP = 1
+      LCN = 1
+      LBN = 1
+      LAN = 1
+      LDCDY = 1
+      LDCDX = 1
+      LKM = 1
+      LTM = 1
+      LVG = 1
+      LUG = 1
+      LVM = 1
+      LUM = 1
+      LHVAR = 1
+      LZET = 1
+      LDEP = 1
+      LVDEP = 1
+      LTSTR = 1
+      LUSTR = 1
+      LOBUK = 1
+      LTAVR = 1
+      LSTEPH = 1
+      LHMIX = 1
+      LZ0 = 1
+      LELEVY = 1
+      LELEVX = 1
+      LELEV = 1
+      LDKZH = 1
+      LDKZM = 1
+      LQ = 1
+      LPSTEP = 1
+      LPI = 1
+      LWZ = 1
+      LVSTEP = 1
+      LVY = 1
+      LUSTEP = 1
+      LUX = 1
+      LTSTEP = 1
+      LPOT = 1
+      LCSTEP = 1
+      LC = 1
+
       CALL BAR2(NX,NY,NZ,NT,NTIME,NWINDX,NWINDY,NSINKS,NFILT,XSTART,
      * YSTART,ZSTART,TSTART,DELTAX,DELTAY,DELTAZ,DELTAT,PHI,DL,
      * DX,DY,DZ,IB,IK,ITY,NCOUNT,NPRINT,NGRAPH,NPSTEP,NGSTEP,LAST,


The initial reason I catched this is that I sometimes run the testsuite with
-fbounds-check, which fails in this case.


-- 
           Summary: gfortran.dg/pr25603.f is invalid code
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: fxcoudert at gcc dot gnu dot org


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