public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94894] New: Premature instantiation of conversion function template during overload resolution Date: Thu, 30 Apr 2020 18:10:07 +0000 [thread overview] Message-ID: <bug-94894-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894 Bug ID: 94894 Summary: Premature instantiation of conversion function template during overload resolution Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- The following testcase was reduced from a build failure with GCC 10 when compiling LLVM. When considering the overload candidate 'void f(int&)' for the overloaded call 'f(S{})', we try to build up a conversion sequence from 'S' to 'int&' that goes through the conversion operator template with T=int. In doing so we instantiate the conversion operator template, which triggers an instantiation of F<int>::k which triggers a hard error. $ cat testcase.C template <typename T, bool B = false> struct F { static_assert(B); }; struct S { template <typename T, int = F<T>::k> operator T(); }; void f(int&); void f(S); void foo() { f(S{}); } $ g++ testcase.C testcase.C: In instantiation of ‘struct F<int, false>’: testcase.C:9:37: required by substitution of ‘template<class T, int <anonymous> > S::operator T() [with T = int; int <anonymous> = <missing>]’ testcase.C:18:6: required from here testcase.C:4:17: error: static assertion failed 4 | static_assert(B); | ^
next reply other threads:[~2020-04-30 18:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-30 18:10 ppalka at gcc dot gnu.org [this message] 2022-07-05 16:08 ` [Bug c++/94894] " redi at gcc dot gnu.org 2022-07-15 15:14 ` [Bug c++/94894] avoidable " ppalka at gcc dot gnu.org 2022-07-19 18:05 ` cvs-commit at gcc dot gnu.org 2024-03-08 21:47 ` ppalka 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-94894-4@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: linkBe 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).