public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53494] [4.7/4.8 Regression] ICE with invalid initializer list Date: Mon, 28 May 2012 16:25:00 -0000 [thread overview] Message-ID: <bug-53494-4-wI59IKEQqN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53494-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53494 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-28 16:21:24 UTC --- 4.6 gets the error right, what you're doing is equivalent to: struct pair { pair(const char*, int) { } }; struct array { pair data[1]; }; array a { { "smile", 1 } }; And that isn't valid. The error 4.6 gives for that is: t.cc:11:26: error: too many initializers for 'pair [1]' t.cc:11:26: error: could not convert '(const char*)"smile"' from 'const char*' to 'pair' Which is very similar to the error 4.6 gives for your original code, except he types in your original are more complicated because they involve templates and typedefs.
next prev parent reply other threads:[~2012-05-28 16:21 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-26 9:40 [Bug c++/53494] New: initializer lists in array type marcus-yass at ihug dot co.nz 2012-05-26 10:10 ` [Bug c++/53494] " paolo.carlini at oracle dot com 2012-05-26 14:54 ` redi at gcc dot gnu.org 2012-05-26 15:16 ` [Bug c++/53494] [4.7/4.8 Regression] ICE with invalid initializer list redi at gcc dot gnu.org 2012-05-26 17:06 ` paolo.carlini at oracle dot com 2012-05-26 20:32 ` marcus-yass at ihug dot co.nz 2012-05-26 21:13 ` paolo.carlini at oracle dot com 2012-05-26 21:47 ` marcus-yass at ihug dot co.nz 2012-05-28 16:17 ` paolo.carlini at oracle dot com 2012-05-28 16:25 ` redi at gcc dot gnu.org [this message] 2012-05-28 16:27 ` redi at gcc dot gnu.org 2012-05-28 16:32 ` paolo.carlini at oracle dot com 2012-05-28 16:41 ` paolo.carlini at oracle dot com 2012-05-28 21:42 ` marcus-yass at ihug dot co.nz 2012-05-29 10:29 ` rguenth at gcc dot gnu.org 2012-05-29 14:22 ` rguenth at gcc dot gnu.org 2012-05-29 22:14 ` daniel.kruegler at googlemail dot com 2012-05-29 22:33 ` paolo.carlini at oracle dot com 2012-05-29 23:15 ` paolo.carlini at oracle dot com 2012-05-29 23:36 ` redi at gcc dot gnu.org 2012-05-29 23:45 ` redi at gcc dot gnu.org 2012-05-30 6:47 ` daniel.kruegler at googlemail dot com 2012-05-30 8:31 ` redi at gcc dot gnu.org 2012-05-30 9:12 ` paolo.carlini at oracle dot com 2012-06-08 9:21 ` paolo.carlini at oracle dot com 2012-06-08 9:27 ` paolo.carlini at oracle dot com 2012-06-14 8:19 ` rguenth at gcc dot gnu.org 2012-08-06 11:58 ` paolo.carlini at oracle dot com 2012-08-06 15:42 ` 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-53494-4-wI59IKEQqN@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).