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:40:46 +0000 [thread overview]
Message-ID: <bug-69636-4-ZSW3tTqJk9@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
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #8)
Commenting out this line:
> private :: cx_plus_int ! <- why does this make a difference?
and adding in the main:
print *, cx_plus_int(a, 2)
make the code compile, while I believe it shouldn't due to the "private"
statement in m. (This version is rejected by other compilers.)
next prev parent reply other threads:[~2023-02-08 20:40 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
2023-02-08 20:40 ` anlauf at gcc dot gnu.org [this message]
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-ZSW3tTqJk9@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).