This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/69054] g++ fails to diagnose ambiguous overload resolution when implicit conversions are involved
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 16 Mar 2017 00:10:34 +0000
- Subject: [Bug c++/69054] g++ fails to diagnose ambiguous overload resolution when implicit conversions are involved
- Auto-submitted: auto-generated
- References: <bug-69054-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69054
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-03-16
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |4.1.3, 4.2.2, 4.3.2, 4.6.0,
| |5.4.0, 6.3.0, 7.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed with today's top of trunk (GCC 7.0) and all released versions.
EDG eccp 4.13 reports:
"t.C", line 19: error: more than one operator "[]" matches these operands:
built-in operator "integer[pointer-to-object]"
function "Something::operator[](const foo &)"
operand types are: Something [ const char [3] ]
d["32"];
^
1 error detected in the compilation of "t.C".