public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "b.j.braams at cwi dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103757] New: compiler rejects import, {none,all,only}, does not recognize the keyword Date: Fri, 17 Dec 2021 10:11:56 +0000 [thread overview] Message-ID: <bug-103757-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103757 Bug ID: 103757 Summary: compiler rejects import, {none,all,only}, does not recognize the keyword Product: gcc Version: 10.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: b.j.braams at cwi dot nl Target Milestone: --- The following code is rejected by gfortran 10.3.1 with an error message "Cannot IMPORT ‘only’ from host scoping unit at (1) - does not exist." Same kind of message if "import, all" or "import, none" is used. It seems that the compiler is interpreting "all", "none" or "only" as objects to be imported rather than as keywords. module moo use iso_fortran_env, only : wp => real64 implicit none ; private public :: foo contains subroutine foo (fun) interface subroutine fun (x) import, only :: wp real (kind=wp) :: x end subroutine fun end interface return end subroutine foo end module moo
next reply other threads:[~2021-12-17 10:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-17 10:11 b.j.braams at cwi dot nl [this message] 2021-12-17 10:16 ` [Bug fortran/103757] " b.j.braams at cwi dot nl 2021-12-17 16:19 ` [Bug fortran/103757] [F18] compiler rejects import, {none, all, only}, " anlauf 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-103757-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: linkBe 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).