public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/69636] ICE(s) on using option -fmodule-private
Date: Wed, 08 Feb 2023 20:10:47 +0000	[thread overview]
Message-ID: <bug-69636-4-vriyEbVaKF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-69636-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from anlauf at gcc dot gnu.org ---
A slightly reduced & rewritten variant of the code in comment#6:

module m
  implicit none
  private
  public  :: cx, operator(+)
  private :: cx_plus_int        ! <- why does this make a difference?
  type cx
    integer :: re
  end type
  interface operator (+)
    module procedure cx_plus_int
  end interface
contains
  function cx_plus_int (z, r)
  entry    int_plus_cx (r, z)   ! <- why does this make a difference?
    type(cx), intent(in) :: z
    integer,  intent(in) :: r
    type(cx)             :: cx_plus_int, int_plus_cx
    cx_plus_int%re = z%re + r
  end function
end module

program p
  use m
  type(cx) :: a = cx(1)
  print *, (a + 2)
end

So there are multiple issues at work:
- the explicit "private :: cx_plus_int" should not make a difference;
  I think I've seen a related PR
- adding an entry that is otherwise unused changes the module
- the modified module when read seems to obstruct finding cx_plus_int,
  although the symbols still appears to be there...

  parent reply	other threads:[~2023-02-08 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-69636-4@http.gcc.gnu.org/bugzilla/>
2023-02-07 21:19 ` anlauf at gcc dot gnu.org
2023-02-08 20:10 ` anlauf at gcc dot gnu.org [this message]
2023-02-08 20:40 ` anlauf at gcc dot gnu.org
2023-02-09 20:22 ` cvs-commit 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-69636-4-vriyEbVaKF@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).