public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61382] parameter pack expansion unexpected order Date: Mon, 30 Jun 2014 14:26:00 -0000 [thread overview] Message-ID: <bug-61382-4-K78kfrmBse@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61382-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61382 --- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> --- Author: jason Date: Mon Jun 30 14:25:21 2014 New Revision: 212150 URL: https://gcc.gnu.org/viewcvs?rev=212150&root=gcc&view=rev Log: DR 1030 PR c++/51253 PR c++/61382 * cp-tree.h (CALL_EXPR_LIST_INIT_P): New. * call.c (struct z_candidate): Add flags field. (add_candidate): Add flags parm. (add_function_candidate, add_conv_candidate, build_builtin_candidate) (add_template_candidate_real): Pass it. (build_over_call): Set CALL_EXPR_LIST_INIT_P. * tree.c (build_aggr_init_expr): Copy it. * semantics.c (simplify_aggr_init_expr): Copy it. * cp-gimplify.c (cp_gimplify_expr): Handle it. Added: branches/gcc-4_9-branch/gcc/testsuite/g++.dg/cpp0x/initlist86.C Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/cp/ChangeLog branches/gcc-4_9-branch/gcc/cp/call.c branches/gcc-4_9-branch/gcc/cp/cp-gimplify.c branches/gcc-4_9-branch/gcc/cp/cp-tree.h branches/gcc-4_9-branch/gcc/cp/semantics.c branches/gcc-4_9-branch/gcc/cp/tree.c branches/gcc-4_9-branch/gcc/gimplify.c branches/gcc-4_9-branch/gcc/gimplify.h
next prev parent reply other threads:[~2014-06-30 14:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-01 21:17 [Bug c++/61382] New: " pengujohn at xvlc dot de 2014-06-01 22:27 ` [Bug c++/61382] " redi at gcc dot gnu.org 2014-06-03 23:03 ` thibaut.lutz at googlemail dot com 2014-06-04 8:50 ` thibaut.lutz at googlemail dot com 2014-06-04 15:51 ` jason at gcc dot gnu.org 2014-06-04 15:52 ` jason at gcc dot gnu.org 2014-06-11 21:35 ` pengujohn at xvlc dot de 2014-06-30 14:26 ` jason at gcc dot gnu.org [this message] 2014-07-03 2:02 ` brooks at gcc dot gnu.org 2014-07-03 3:37 ` brooks at gcc dot gnu.org 2014-07-03 8:29 ` jakub at gcc dot gnu.org 2014-07-04 7:24 ` jason at gcc dot gnu.org 2014-07-04 8:24 ` jakub at gcc dot gnu.org 2014-07-08 2:57 ` brooks at gcc dot gnu.org 2014-07-08 22:34 ` jason 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-61382-4-K78kfrmBse@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).