public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arjen Markus <arjen.markus895@gmail.com>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re:
Date: Sun, 26 Jul 2020 10:55:07 +0200	[thread overview]
Message-ID: <CAMCbSMqciS50bipeBj6KfQddkva=USbtRw-FZmuU_DX683Rhsw@mail.gmail.com> (raw)
In-Reply-To: <CACR8rveH-55a4AmEk=wdZaTUWaOTMU0FROFvBz9ENH+sxpvhpg@mail.gmail.com>

I tried this with Intel Fortran and that accepts the code as well.
Variations in the code do not resolve the problem (different basic
type for arg, using dimension(:), without the nopass attribute).

I suggest you create a PR for this.

Regards,

Arjen

Op zo 26 jul. 2020 om 06:50 schreef Damian Rouson
<damian@sourceryinstitute.org>:
>
> I believe the gfortran error message below is incorrect.  Gfotran 8, 9 and
> 10 give the same message.  The code below compiles cleanly with the NAG
> Fortran compiler.
>
> Damian
>
> ± cat shape-mismatch.f90
> module foobar
>   type foo
>   contains
>     procedure, nopass :: bar
>   end type
>   interface
>     module subroutine bar(arg)
>       character(len=*) arg(:)
>     end subroutine
>   end interface
> contains
>   module procedure bar
>   end procedure
> end module
>
> ± gfortran -c shape-mismatch.f90
> shape-mismatch.f90:12:22:
>
>    12 |   module procedure bar
>       |                      1
> Error: Shape mismatch in argument 'arg' at (1)
>
> ± gfortran --version
> GNU Fortran (GCC) 10.1.0

  reply	other threads:[~2020-07-26  8:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  4:49 Damian Rouson
2020-07-26  8:55 ` Arjen Markus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-22 13:06 Mamadou Diop
2023-08-23  8:19 ` Arjen Markus
2021-03-10 18:34 mscfd
2021-03-11  7:48 ` Richard Biener
2013-03-13  5:51 Re: DavidLNewton
2013-03-12  9:22 Re: DavidLNewton
2007-07-06  6:27 Re: Tobias Burnus
2007-07-06  8:17 ` Re: Lee Millward
     [not found] <8C94B5ACA298987-8B4-8502@WEBMAIL-DB13.sysops.aol.com>
2007-04-12 21:00 ` Re: FX Coudert
2007-03-27 13:13 Re: Paul Richard Thomas
     [not found] <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
2003-12-07 14:17 ` Re: Paul Brook

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='CAMCbSMqciS50bipeBj6KfQddkva=USbtRw-FZmuU_DX683Rhsw@mail.gmail.com' \
    --to=arjen.markus895@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@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).