This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/10965] New: g77 compiles illegal code in testsuite
- From: "billingd at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 May 2003 11:04:27 -0000
- Subject: [Bug fortran/10965] New: g77 compiles illegal code in testsuite
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10965
Summary: g77 compiles illegal code in testsuite
Product: gcc
Version: 3.4
Status: NEW
Severity: normal
Priority: P2
Component: fortran
AssignedTo: billingd@gcc.gnu.org
ReportedBy: billingd@gcc.gnu.org
CC: gcc-bugs@gcc.gnu.org
Steve Kargl reported a problem with 20000601-2.f. The test is one of mine. I
will check over my notes and come up with a fix.
I'm running the Fortran 77 code in gcc-testsuite-3.3.tar.bz2
through g95 and I've found that 20000601-2.f contains
illegal code for Fortran 95 and probably Fortran 77. I don't
have the Fortran 77 standard handy, but I believe the code is
illegal; yet g77 compiles the code without warning or error.
kargl[303] f77 -v -c 20000601-2.f
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.2.2 [FreeBSD] 20030205 (release)
kargl[305] f95 -V -fixed -dusty 20000601-2.f
NAGWare Fortran 95 compiler Release 4.2(468)
Copyright 1990-2002 The Numerical Algorithms Group Ltd., Oxford, U.K.
f95comp version is 4.2(468)
Warning: 20000601-2.f, line 27: Unused symbol WORK31
detected at END@<end-of-statement>
Warning: 20000601-2.f, line 27: Unused symbol WORK13
detected at END@<end-of-statement>
[f95 continuing despite warning messages]
Obsolescent: 20000601-2.f, line 1: Fixed source form
Error: 20000601-2.f, line 21: Inconsistent argument data types to intrinsic MAX
kargl[318] ../../../../bin/g95 -ffixed-form -c -x f95 20000601-2.f
In file 20000601-2.f:21
JP = MAX( KM+1, AB( KV+1, JJ ) )
1
Error: 'a2' argument of 'max' intrinsic at (1) must be INTEGER(4)
--
Steve
http://troutmask.apl.washington.edu/~kargl/
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.