public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "damian at sourceryinstitute dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96320] gfortran 8-10 shape mismatch in assumed-length dummy argument character array
Date: Sat, 15 Aug 2020 01:59:01 +0000	[thread overview]
Message-ID: <bug-96320-4-EQWA50aHLc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96320-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96320

--- Comment #23 from Damian Rouson <damian at sourceryinstitute dot org> ---
A related issue arises if the procedure in question is a pure function as
demonstrated below.  The code compiles cleanly if either
1. The result-spec is absent and the procedure is renamed new_foo in both the
interface body and in the procedure definition, or
2. The interface body is repeated in the procedure definition instead the
"module procedure" syntax.

± cat pure-shape-mismatch.f90 
module foobar
  implicit none

  type foo
    integer bar
  end type

  interface
    pure module function create() result(new_foo)
      implicit none
      type(foo) new_foo
    end function
  end interface

contains
  module procedure create
    new_foo%bar = 1
  end procedure
end module 

± gfortran -c pure-shape-mismatch.f90 
pure-shape-mismatch.f90:17:4:

   17 |     new_foo%bar = 1
      |    1
Error: Variable ‘new_foo’ cannot appear in a variable definition context
(assignment) at (1) in PURE procedure

± gfortran --version
GNU Fortran (GCC) 11.0.0 20200804 (experimental)

  parent reply	other threads:[~2020-08-15  1:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  4:47 [Bug fortran/96320] New: " damian at sourceryinstitute dot org
2020-07-26 16:34 ` [Bug fortran/96320] " dominiq at lps dot ens.fr
2020-07-26 16:44 ` damian at sourceryinstitute dot org
2020-07-26 16:54 ` dominiq at lps dot ens.fr
2020-07-26 18:43 ` kargl at gcc dot gnu.org
2020-07-26 19:13 ` kargl at gcc dot gnu.org
2020-07-26 21:35 ` jvdelisle at charter dot net
2020-07-27  0:39 ` damian at sourceryinstitute dot org
2020-07-27  0:45 ` sgk at troutmask dot apl.washington.edu
2020-07-27  3:34 ` damian at sourceryinstitute dot org
2020-07-27  7:26 ` pault at gcc dot gnu.org
2020-07-27 11:37 ` dominiq at lps dot ens.fr
2020-07-27 17:26 ` pault at gcc dot gnu.org
2020-07-27 18:12 ` damian at sourceryinstitute dot org
2020-07-27 19:03 ` dominiq at lps dot ens.fr
2020-07-28  9:24 ` dominiq at lps dot ens.fr
2020-07-28  9:43 ` paul.richard.thomas at gmail dot com
2020-07-28 10:32 ` dominiq at lps dot ens.fr
2020-07-28 14:13 ` sgk at troutmask dot apl.washington.edu
2020-07-28 15:18 ` dominiq at lps dot ens.fr
2020-08-02 10:00 ` cvs-commit at gcc dot gnu.org
2020-08-02 10:05 ` pault at gcc dot gnu.org
2020-08-03 23:45 ` damian at sourceryinstitute dot org
2020-08-04  1:53 ` sgk at troutmask dot apl.washington.edu
2020-08-15  1:59 ` damian at sourceryinstitute dot org [this message]
2020-08-20 17:17 ` damian at sourceryinstitute dot org
2020-12-28 14:55 ` cvs-commit at gcc dot gnu.org
2021-01-04 14:42 ` cvs-commit at gcc dot gnu.org
2021-01-04 15:15 ` pault at gcc dot gnu.org
2021-01-21 10:01 ` cvs-commit at gcc dot gnu.org
2023-10-31 14:17 ` pault at gcc dot gnu.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-96320-4-EQWA50aHLc@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).