public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61723] [C++11] ICE in contains_struct_check Date: Tue, 15 Jul 2014 14:09:00 -0000 [thread overview] Message-ID: <bug-61723-4-oVXMM7llE6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61723-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61723 Paolo Carlini <paolo.carlini at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> --- I find this testcase rather weird: std::initializer_list isn't a random user type: we have non-trivial "magic" in the front-end which *assumes* the actual definition in our <initializer_list> header. You can see this in the testcase here too, because the ICEs disappear if _M_len is declared as an (unsigned) __SIZE_TYPE__ (not as an int) and an additional field _M_array is added too (see our actual std::initializer_list for details). If you ask me, the Bug Report seems invalid to me or at least very low priority, unless a version of it not redefining std::initializer_list exists.
next prev parent reply other threads:[~2014-07-15 14:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-05 18:58 [Bug c++/61723] New: " ppluzhnikov at google dot com 2014-07-15 14:09 ` paolo.carlini at oracle dot com [this message] 2014-07-15 15:22 ` [Bug c++/61723] " jason at gcc dot gnu.org 2014-07-15 19:17 ` jason at gcc dot gnu.org 2014-07-15 19:37 ` jason at gcc dot gnu.org 2014-07-15 20:51 ` ppluzhnikov at google dot com 2014-07-31 13:34 ` paolo.carlini at oracle dot com 2014-12-12 18:53 ` 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-61723-4-oVXMM7llE6@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).