public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29411] unique overload sets for extern "C" vs. C++ function pointers
Date: Tue, 10 Oct 2006 16:34:00 -0000 [thread overview]
Message-ID: <20061010163347.12923.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29411-365@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2006-10-10 16:33 -------
This is really a dup of bug 2316. I forgot to mention that in PR 29095.
Oh and this is not an enhancement because you can have wrong code and also
rejects valid testcases see the dup bug report about those cases.
*** This bug has been marked as a duplicate of 2316 ***
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29411
prev parent reply other threads:[~2006-10-10 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 10:07 [Bug c++/29411] New: " bkoz at gcc dot gnu dot org
2006-10-10 10:09 ` [Bug c++/29411] " bkoz at gcc dot gnu dot org
2006-10-10 16:34 ` pinskia at gcc dot gnu dot org [this message]
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=20061010163347.12923.qmail@sourceware.org \
--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).