public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114438] New: Missed constraint F2023:c7108 Date: Fri, 22 Mar 2024 23:13:44 +0000 [thread overview] Message-ID: <bug-114438-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 Bug ID: 114438 Summary: Missed constraint F2023:c7108 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Created attachment 57785 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57785&action=edit Fortran 2023:C7108 violation Gfortran does not diagnosis F2023:C7108. C7108 (R756) If derived-type-spec is a type name that is the same as a generic name, the component-spec-list shall not be a valid actual-arg-spec-list for a function reference that is resolvable as a generic reference to that name (15.5.5.2). The attached program compiles and execute where the generic function is resolved to a function.
next reply other threads:[~2024-03-22 23:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-22 23:13 kargl at gcc dot gnu.org [this message] 2024-03-22 23:14 ` [Bug fortran/114438] " kargl at gcc dot gnu.org 2024-03-23 19:36 ` anlauf at gcc dot gnu.org 2024-03-23 19:56 ` kargl at gcc dot gnu.org 2024-03-23 20:11 ` anlauf at gcc dot gnu.org 2024-03-23 20:53 ` kargl at gcc dot gnu.org 2024-03-23 21:15 ` kargl at gcc dot gnu.org 2024-03-24 2:49 ` 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-114438-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).