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/113997] Bogus 'Warning: Interface mismatch in global procedure' with C binding
Date: Mon, 19 Feb 2024 17:34:59 +0000 [thread overview]
Message-ID: <bug-113997-4-4ce5PoHHC3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113997-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113997
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
Can you provide a complete minimum example? It seems that your
description conflicts with Fortran 2023, 19.2 Global identifiers.
1 ... entities with binding labels ... are global entities of a program.
... The name of ... external procedure with no binding label ... is a
global
identifier. ... A binding label of an entity of the program is a global
identifier.
2 The global identifier of an entity shall not be the same as the global
identifier
of any other entity. Furthermore, a binding label shall not be the same as
the
global identifier of any other global entity, ignoring differences in case.
next prev parent reply other threads:[~2024-02-19 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:37 [Bug fortran/113997] New: " burnus at gcc dot gnu.org
2024-02-19 17:34 ` kargl at gcc dot gnu.org [this message]
2024-02-19 17:55 ` [Bug fortran/113997] " anlauf at gcc dot gnu.org
2024-02-19 18:13 ` burnus at gcc dot gnu.org
2024-02-19 18:19 ` anlauf at gcc dot gnu.org
2024-02-19 18:28 ` 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-113997-4-4ce5PoHHC3@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).