https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Richard Biener from comment #6) > This seems to be kind-of SUSPENDED if the standard is ambiguous. It might > be reasonable to go back to the previous behavior for the ambiguous case. I didn't mean that the standard was ambiguous, it seems clear to me that the call is ambiguous under the final resolution of CWG2273, which suggests INVALID. But SUSPENDED might be appropriate given that Clang/EDG/MSVC all disagree. > Doesn't seem to be P1-ish though, as still UNCONFIRMED. I've been hoping for input from other implementers as to why nobody else rejects this testcase, but nobody has replied yet to my Friday email.
