public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malaperle at omnialabs dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50306] ambiguous templated conversion operators accepted
Date: Sat, 19 Nov 2011 08:12:00 -0000	[thread overview]
Message-ID: <bug-50306-4-Y4H8IMO5mm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50306-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Marc-Andre Laperle <malaperle at omnialabs dot net> 2011-11-19 05:38:32 UTC ---
I tried 4.6.2, r181503 and r180166 and they all compiled the sample code
without error. Do you have any local changes or special parameters that made it
not compile?


  parent reply	other threads:[~2011-11-19  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 17:21 [Bug c++/50306] New: g++ accepts code with ambiguous, templated conversion operators malaperle at omnialabs dot net
2011-11-17 18:06 ` [Bug c++/50306] ambiguous templated conversion operators accepted malaperle at omnialabs dot net
2011-11-17 19:05 ` manu at gcc dot gnu.org
2011-11-19  8:12 ` malaperle at omnialabs dot net [this message]
2011-11-19 12:46 ` paolo.carlini at oracle dot com
2011-11-19 13:57 ` manu 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-50306-4-Y4H8IMO5mm@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).