public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "toon at moene dot indiv dot nluug dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16511] Test 19990905-0.f fails with gfortran
Date: Tue, 13 Jul 2004 20:37:00 -0000 [thread overview]
Message-ID: <20040713203714.24426.qmail@sourceware.org> (raw)
In-Reply-To: <20040713055437.16511.billingd@gcc.gnu.org>
------- Additional Comments From toon at moene dot indiv dot nluug dot nl 2004-07-13 20:37 -------
Subject: Re: New: Test 19990905-0.f fails with gfortran
billingd at gcc dot gnu dot org wrote:
> g77 test 19990905-0.f fails with gfortran.
>
> The test is
>
> c { dg-do compile }
> * =foo0.f in Burley's g77 test suite.
> subroutine sub(a)
> common /info/ iarray(1000)
> equivalence (m,iarray(100)), (n,iarray(200))
> real a(m,n)
> a(1,1) = a(2,2)
> end
>
> In file /usr/local/src/gcc/gcc/testsuite/gfortran.dg/g77/19990905-0.f:6
>
> real a(m,n)
> 1
> Error: Variable 'm' cannot appear in the expression at (1)
>
> According to Steve Kargl:
>
> Ftnchek says its legal Fortran 77.
That can't be true, because it isn't - my take on it is that ftnchek
simply doesn't recognise the issues.
m is equivalenced to an item in common. That makes `real a(m,n)' a
declaration of an automatic array, which is a Fortran 90 beast (it
didn't exist in Fortran 77)
However, to me it looks like a valid (though complicated) way to define
such a thing.
Hope this helps,
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16511
next prev parent reply other threads:[~2004-07-13 20:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 5:54 [Bug fortran/16511] New: " billingd at gcc dot gnu dot org
2004-07-13 5:56 ` [Bug fortran/16511] " billingd at gcc dot gnu dot org
2004-07-13 7:09 ` cvs-commit at gcc dot gnu dot org
2004-07-13 13:48 ` pinskia at gcc dot gnu dot org
2004-07-13 20:37 ` [Bug fortran/16511] New: " Toon Moene
2004-07-13 20:37 ` toon at moene dot indiv dot nluug dot nl [this message]
2004-07-14 1:13 ` [Bug fortran/16511] " billingd at gcc dot gnu dot org
2004-07-14 3:26 ` billingd at gcc dot gnu dot org
2004-07-14 12:03 ` tobi at gcc dot gnu dot org
2004-07-15 0:32 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-07-15 23:22 ` billingd at gcc dot gnu dot org
2004-12-10 8:56 ` paulthomas2 at wanadoo dot fr
2005-01-06 14:42 ` tobi at gcc dot gnu dot org
2005-01-06 15:56 ` coudert at clipper dot ens dot fr
2005-01-06 16:11 ` tobi at gcc dot gnu dot org
2005-03-10 14:38 ` pinskia at gcc dot gnu dot org
2005-03-10 14:39 ` pinskia at gcc dot gnu dot org
2005-09-09 0:25 ` cvs-commit at gcc dot gnu dot org
2005-09-09 9:07 ` cvs-commit at gcc dot gnu dot org
2005-09-09 22:15 ` pinskia at gcc dot gnu dot 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=20040713203714.24426.qmail@sourceware.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: 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).