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++/48531] [C++0x][SFINAE] Hard errors with arrays of unknown bound Date: Thu, 14 Apr 2011 23:00:00 -0000 [thread overview] Message-ID: <bug-48531-4-MQ9iV5eG3z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48531-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48531 --- Comment #4 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-04-14 23:00:05 UTC --- (In reply to comment #3) Here is a minimalistic example that provokes the same error. The essence is, that the construction expression is evaluated combined with another construction or destruction expression in a single (constant) expression. The other expressions seems not relevant, it can even be the same expression, like here: //------------------- template<class T, class = decltype(T()) > char f(int); template<class> double f(...); struct B2 { B2(...); }; constexpr bool b = sizeof(f<B2[1]>(0)) == 1 && sizeof(f<B2[1]>(0)) == 1; //------------------- "main.cpp:13:37: internal compiler error: in build_value_init_noctor, at cp/init.c:455" Another example case is, when we combine a destructor expression with a constructor expression like this (Note that B1 is a slightly differently here): template<class T, class = decltype(T()) > char f(int); template<class> double f(...); template<class T> T&& create(); template<class T, class = decltype(create<T&>().~T()) > char g(int); template<class> double g(...); template<class... T> struct B1 { B1(T...); }; constexpr bool b = sizeof(g<B1<>[1]>(0)) == 1 && sizeof(f<B1<>[1]>(0)) == 1; This gives exactly the same error: "main.cpp:31:69: internal compiler error: in build_value_init_noctor, at cp/init.c:455" In addition to the ICE the new code gives incorrect results for an array with known bounds of type with deleted d'tor. Given the same f as defined above (testing for default construction): struct D { ~D() = delete; }; static_assert(sizeof(f<D[1]>(0)) != 1, "Error"); the static assertion fires.
next prev parent reply other threads:[~2011-04-14 23:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-09 17:09 [Bug c++/48531] New: " daniel.kruegler at googlemail dot com 2011-04-14 15:00 ` [Bug c++/48531] " jason at gcc dot gnu.org 2011-04-14 15:11 ` jason at gcc dot gnu.org 2011-04-14 17:56 ` paolo.carlini at oracle dot com 2011-04-14 23:00 ` daniel.kruegler at googlemail dot com [this message] 2011-04-14 23:06 ` paolo.carlini at oracle dot com 2011-04-18 0:51 ` jason at gcc dot gnu.org 2011-04-18 4:23 ` jason at gcc dot gnu.org 2011-04-18 11:05 ` paolo.carlini at oracle dot com 2011-04-18 11:13 ` daniel.kruegler at googlemail dot com 2011-04-18 11:36 ` paolo.carlini at oracle dot com 2011-04-18 11:48 ` daniel.kruegler at googlemail dot com 2011-04-18 12:17 ` 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-48531-4-MQ9iV5eG3z@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).