public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53349] Internal compiler error with constexpr and recursive data type. Date: Tue, 15 May 2012 11:19:00 -0000 [thread overview] Message-ID: <bug-53349-4-lXM9ahKqW7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53349-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53349 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler at | |googlemail dot com --- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2012-05-15 10:53:22 UTC --- I can confirm this for gcc 4.8.0 20120513 (experimental). A current workaround is to replace the member declaration constexpr Foo(const Foo<N-1> a) : m_a(a) {} by constexpr Foo(const Foo<N-1>& a) : m_a(a) {} The following is a simplified form of the problem: template<int N> struct Foo { constexpr Foo(const Foo<N-1> a) : m_a(a) {} // Line 3 constexpr Foo(const Foo<N> &a) : m_a(a.m_a) {} Foo<N-1> m_a; }; template <> struct Foo<0> {}; constexpr auto res = Foo<2>(Foo<1>(Foo<0>())); // Line 10 10| in constexpr expansion of 'Foo<2>(Foo<1>((*(const Foo<1>*)(& Foo<1>((Foo<0>((* & Foo<0>())), Foo<0>()))))))'| 3| in constexpr expansion of '((Foo<2>*)this)->Foo<2>::m_a.Foo<N>::Foo<1>((* & a))'| 10|internal compiler error: in cxx_eval_indirect_ref, at cp/semantics.c:7408|
next prev parent reply other threads:[~2012-05-15 10:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-14 22:21 [Bug c++/53349] New: " pkeir at dcs dot gla.ac.uk 2012-05-15 11:19 ` daniel.kruegler at googlemail dot com [this message] 2012-05-20 20:00 ` [Bug c++/53349] " pinskia at gcc dot gnu.org 2013-08-11 22:08 ` paolo.carlini at oracle dot com
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-53349-4-lXM9ahKqW7@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).