From: Bud Davis <bdavis9659@comcast.net>
To: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: g77 compiles illegal code in testsuite?
Date: Fri, 23 May 2003 15:36:00 -0000 [thread overview]
Message-ID: <3ECE3F59.60907@comcast.net> (raw)
In-Reply-To: <200305231507.h4NF7BW7001016@troutmask.apl.washington.edu>
Steven G. Kargl wrote:
>Bud Davis said:
>
>
>>| 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.
>>
>>
>>
>
>[Table of intrinsics snipped]
>
>
>
>>In my interpretation, the code in question is not valid.
>>MAX is the generic name for MAX0,AMAX1, and DMAX1,
>>
>>
>
>This is correct.
>
>
>
>>not for AMAX0 which is the specfic intrinisic needed here.
>>
>>
>
>Actually, I beleive AMAX0 would also be wrong. The arguments
>of AMAX0 must have the same type.
>
>
>
>>
>>Maybe g77 should issue a warning (when invoked with -fpedantic) ?
>>
>>
>>
>
>It's Toon's call, but I think g77 should issue an error and
>abort. The g77 info contains a -fno-ugly-args option. I
>would think you should need -fugly-args to compile the code
>in question.
>
>
>
>>Of course, IMHO, g95 should be backwards compatable with g77 :)
>>
>>
>
>This may not happen, because Fortran 95 has deleted a few
>features from Fortran 77.
>
>
>
quite right about AMAX0. it would not be correct. i read the table wrong :)
--bud davis
next prev parent reply other threads:[~2003-05-23 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 12:57 Bud Davis
2003-05-23 14:23 ` Paul Brook
2003-05-23 15:15 ` Steven G. Kargl
2003-05-23 15:36 ` Bud Davis [this message]
2003-05-23 22:57 ` Toon Moene
2003-05-23 23:40 ` Steven Bosscher
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 3:33 Steven G. Kargl
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=3ECE3F59.60907@comcast.net \
--to=bdavis9659@comcast.net \
--cc=gcc@gcc.gnu.org \
--cc=kargl@troutmask.apl.washington.edu \
/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: link
Be 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).