public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot a dot richmond at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31564]  New: Error: Type/rank mismatch in argument
Date: Fri, 13 Apr 2007 17:48:00 -0000	[thread overview]
Message-ID: <bug-31564-14284@http.gcc.gnu.org/bugzilla/> (raw)

When I compile the module listed below I get the message:

c3.f90:15.23:
        USE cdf_aux_mod
                      1
Error: Type/rank mismatch in argument 'arg_name' at (1)

g95 and Lahey do not produce error messages. Is it legal?

    MODULE cdf_aux_mod
      TYPE :: the_distribution
        INTEGER :: parameters(1)
      END TYPE the_distribution
      TYPE (the_distribution), PARAMETER :: the_beta = the_distribution((/0/))
    CONTAINS
      SUBROUTINE set_bound(arg_name)
        INTEGER, INTENT (IN) :: arg_name
      END SUBROUTINE set_bound
    END MODULE cdf_aux_mod
    MODULE cdf_beta_mod
    CONTAINS
      SUBROUTINE cdf_beta()
        USE cdf_aux_mod
        INTEGER :: which
          CALL set_bound(the_beta%parameters(which))
      END SUBROUTINE cdf_beta
    END MODULE cdf_beta_mod


-- 
           Summary: Error: Type/rank mismatch in argument
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: michael dot a dot richmond at nasa dot gov


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


             reply	other threads:[~2007-04-13 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 17:48 michael dot a dot richmond at nasa dot gov [this message]
2007-04-13 18:05 ` [Bug fortran/31564] " kargl at gcc dot gnu dot org
2007-04-13 18:40 ` burnus at gcc dot gnu dot org
2007-04-22 17:49 ` eedelman at gcc dot gnu dot org
2007-05-27 23:40 ` burnus at gcc dot gnu dot org
2007-05-28 15:41 ` eedelman at gcc dot gnu dot org
2007-05-28 18:51 ` eedelman at gcc dot gnu dot org
2007-06-03 19:28 ` eedelman at gcc dot gnu dot org
2007-08-18  6:04 ` pault at gcc dot gnu dot org
2007-09-04 18:16 ` pault at gcc dot gnu dot org
2007-09-05 13:35 ` pault at gcc dot gnu dot org
2007-09-05 13:38 ` pault at gcc dot gnu dot org
2007-09-06 11:56 ` patchapp at dberlin 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=bug-31564-14284@http.gcc.gnu.org/bugzilla/ \
    --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).