public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juno.krahn at nih dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55465] Name collision in C binding (calling C from Fortran)
Date: Mon, 26 Nov 2012 19:52:00 -0000	[thread overview]
Message-ID: <bug-55465-4-8H6Vj6ze0h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55465-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55465

Juno Krahn <juno.krahn at nih dot gov> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juno.krahn at nih dot gov

--- Comment #7 from Juno Krahn <juno.krahn at nih dot gov> 2012-11-26 19:51:55 UTC ---
IMHO, this is valid code regardless of whether the binary argument types can be
seen as equivalent. The standard is quite vague, but see my comment at bug
48858 comment 13. The standard defines that the binding label itself is a
unique global entity, but does not specify that the interface definition is
unique.


  parent reply	other threads:[~2012-11-26 19:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 18:19 [Bug fortran/55465] New: " fmartinez at gmv dot com
2012-11-25 18:20 ` [Bug fortran/55465] " fmartinez at gmv dot com
2012-11-25 18:21 ` fmartinez at gmv dot com
2012-11-26 16:38 ` janus at gcc dot gnu.org
2012-11-26 17:08 ` janus at gcc dot gnu.org
2012-11-26 17:36 ` fmartinez at gmv dot com
2012-11-26 17:41 ` burnus at gcc dot gnu.org
2012-11-26 19:52 ` juno.krahn at nih dot gov [this message]
2012-11-26 19:55 ` juno.krahn at nih dot gov
2012-11-26 20:20 ` anlauf at gmx dot de
2012-11-26 20:25 ` anlauf at gmx dot de
2012-11-26 20:58 ` anlauf at gmx dot de
2012-11-27  9:49 ` fmartinez at gmv dot com
2012-11-30 17:21 ` juno.krahn at nih dot gov
2013-05-20 20:14 ` burnus at gcc dot gnu.org
2013-05-20 20:18 ` burnus at gcc dot gnu.org
2013-05-22  6:39 ` burnus 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-55465-4-8H6Vj6ze0h@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).