public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "everythingfunctional at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105594] New: -Wuse-without-only issued for any submodule Date: Fri, 13 May 2022 16:00:31 +0000 [thread overview] Message-ID: <bug-105594-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105594 Bug ID: 105594 Summary: -Wuse-without-only issued for any submodule Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: everythingfunctional at protonmail dot com Target Milestone: --- The -Wuse-without-only option issues a warning when compiling any submodule. This is incorrect as a submodule statement is not a use statement, and cannot contain an only qualifier. For example the source code module foo_m interface module subroutine foo end subroutine end interface end module submodule (foo_m) foo_s contains module procedure foo end procedure end submodule when compiled like $ gfortran -c -Wuse-without-only foo_m.f90 foo_m.f90:8:17: 8 | submodule (foo_m) foo_s | 1 Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
next reply other threads:[~2022-05-13 16:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-13 16:00 everythingfunctional at protonmail dot com [this message] 2022-05-13 17:17 ` [Bug fortran/105594] " kargl at gcc dot gnu.org 2023-05-30 0:03 ` kargl 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-105594-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).