This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/55465] Name collision in C binding (calling C from Fortran)
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 22 May 2013 06:39:49 +0000
- Subject: [Bug fortran/55465] Name collision in C binding (calling C from Fortran)
- Auto-submitted: auto-generated
- References: <bug-55465-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55465
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed| |2013-05-22
Resolution|FIXED |---
Ever confirmed|0 |1
--- Comment #16 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Juno Krahn from comment #13)
> This issue was once discussed by members of the Fortran standards committee.
> I don't recall if that was on usenet or somewhere in the committee meeting
> notes. The conclusion was that it is useful to allow for multiple explicit
> interfaces in order to interface correctly with C libraries, and that the
> standards allow for it.
Well, at least some standard committee members believe that the code in comment
0 is invalid: http://mailman.j3-fortran.org/pipermail/j3/2013-May/006397.html
Let's open this PR - and use it to track the addition of some diagnostic. It
might be a warning or error, it might depend on -std= or not.