public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "billingd@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/10965] New: g77 compiles illegal code in testsuite Date: Sat, 24 May 2003 11:44:00 -0000 [thread overview] Message-ID: <20030524110427.10965.billingd@gcc.gnu.org> (raw) 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.
next reply other threads:[~2003-05-24 11:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-24 11:44 billingd@gcc.gnu.org [this message] 2003-05-24 14:04 ` [Bug fortran/10965] " billingd@gcc.gnu.org 2003-05-27 0:36 ` david.billinghurst@riotinto.com 2003-06-03 0:15 ` billingd@gcc.gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030524110427.10965.billingd@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).