public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/26227] accepts invalid fortran, different dummy types/number
Date: Thu, 05 Apr 2007 12:27:00 -0000	[thread overview]
Message-ID: <20070405122736.23501.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26227-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from burnus at gcc dot gnu dot org  2007-04-05 13:27 -------
This probably will work automatically if inter-file checking is implemented,
but if not, here is an invalid example which should be rejected:
---------
      SUBROUTINE PHLOAD (READER,*)
      IMPLICIT NONE
      EXTERNAL         READER
      CALL READER (*1)
 1    RETURN 1
      END SUBROUTINE

      program test
      EXTERNAL R
      call PHLOAD (R, 1)
      CALL PHLOAD (R, 2)
      END program test
---------

Should give the error (cf. NAG f95):

Error: y.f: Argument no. 2 in reference to PHLOAD from TEST is not a label


-- 


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


  parent reply	other threads:[~2007-04-05 12:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 21:23 [Bug fortran/26227] New: " pinskia at gcc dot gnu dot org
2006-04-04  1:37 ` [Bug fortran/26227] " pinskia at gcc dot gnu dot org
2006-04-04  4:42 ` paulthomas2 at wanadoo dot fr
2006-05-13 22:26 ` pinskia at gcc dot gnu dot org
2006-05-13 23:05 ` pinskia at gcc dot gnu dot org
2006-05-13 23:19 ` pinskia at gcc dot gnu dot org
2006-09-13 16:11 ` tobi at gcc dot gnu dot org
2006-09-13 16:12 ` tobi at gcc dot gnu dot org
2007-03-12 19:09 ` burnus at gcc dot gnu dot org
2007-04-05 12:27 ` burnus at gcc dot gnu dot org [this message]
2007-06-01 15:21 ` burnus at gcc dot gnu dot org
2009-03-30 19:36 ` pault at gcc dot gnu dot org
2009-03-30 22:01 ` dominiq at lps dot ens dot fr
2010-05-19 21:54 ` tkoenig at gcc dot gnu dot org
2010-05-24 14:03 ` dfranke 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=20070405122736.23501.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).