[Bug c++/82579] GCC 7/8 ambiguous call to overload

2017-10-17 Thread ostash at ostash dot kiev.ua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82579 Viktor Ostashevskyi changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c++/82579] GCC 7/8 ambiguous call to overload

2017-10-17 Thread ostash at ostash dot kiev.ua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82579 Viktor Ostashevskyi changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/82579] GCC 7/8 ambiguous call to overload

2017-10-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82579 --- Comment #1 from Jonathan Wakely --- This is not a GCC bug, because it's the required behaviour for C++17. Use -fno-new-ttp-matching to disable it in C++17 (or use -fnew-ttp-matching to enable it in C++14 and make it ambiguous).