public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neil.n.carlson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104630] New: module subroutine not accessible from submodule
Date: Tue, 22 Feb 2022 05:46:23 +0000	[thread overview]
Message-ID: <bug-104630-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104630
           Summary: module subroutine not accessible from submodule
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: neil.n.carlson at gmail dot com
  Target Milestone: ---

Consider this minimal example.

File module.f90:
  module modA
    private
    type, public :: typeA
    contains
      procedure :: foo
    end type
    interface
      module subroutine foo(this)
        class(typeA) :: this
      end subroutine
    end interface
  contains
    subroutine bar(this)
      type(typeA) :: this
    end subroutine
  end module

File submodule.f90:
  submodule(modA) foo_impl
  contains
    module subroutine foo(this)
      class(typeA) :: this
      call bar(this) ! a module subroutine in the host module
    end subroutine
  end submodule

File main.f90:
  use modA
  end

The implementation of subroutine foo in the submodule should have
access to subroutine bar defined in its host module but it apparently
does not judging from the link error:

$ gfortran module.f90 submodule.f90 main.f90
/usr/bin/ld: /tmp/ccEycu6t.o: in function `__moda_MOD_foo':
gfortran-20220221-submodule.f90:(.text+0x17): undefined reference to
`__moda_MOD_bar'
collect2: error: ld returned 1 exit status

If the 3 program units are combined into a single file, that will
compile and link without error.

             reply	other threads:[~2022-02-22  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  5:46 neil.n.carlson at gmail dot com [this message]
2022-05-24 19:37 ` [Bug fortran/104630] " kargl at gcc dot gnu.org
2022-11-16 23:48 ` jwmwalrus at gmail dot com
2023-06-30 13:58 ` daryl.00179 at gmail dot com

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-104630-4@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).