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++/35722] [C++0x] Variadic templates expansion into non-variadic class template Date: Sun, 02 Oct 2011 21:46:00 -0000 [thread overview] Message-ID: <bug-35722-4-E5AYEYWLNv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-35722-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35722 --- Comment #16 from Jason Merrill <jason at gcc dot gnu.org> 2011-10-02 21:45:08 UTC --- Author: jason Date: Sun Oct 2 21:45:01 2011 New Revision: 179436 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179436 Log: PR c++/35722 Implement N2555 (expanding pack expansion to fixed parm list) * pt.c (coerce_template_parms): Allow expanding a pack expansion to a fixed-length argument list. (unify_pack_expansion): Handle explicit args properly. (unify) [TREE_VEC]: Handle pack expansions here. [TYPE_ARGUMENT_PACK]: Not here. (tsubst_pack_expansion): Don't try to do partial substitution. (pack_deducible_p): New. (fn_type_unification): Use it. (find_parameter_packs_r): Take the TYPE_MAIN_VARIANT of a type parameter. (check_non_deducible_conversion): Split from type_unification_real. (unify_one_argument): Split from type_unification_real... (unify_pack_expansion): ...and here. Drop call_args_p parm. (type_unification_real, unify, more_specialized_fn): Adjust. Added: trunk/gcc/testsuite/g++.dg/cpp0x/variadic-explicit1.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic-nondeduce1.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic117.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic118.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/pt.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/cpp0x/variadic105.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic35.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic65.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic82.C trunk/gcc/testsuite/g++.dg/cpp0x/variadic83.C trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/testsuite/util/testsuite_tr1.h
next prev parent reply other threads:[~2011-10-02 21:46 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-35722-4@http.gcc.gnu.org/bugzilla/> 2011-01-04 22:53 ` dodji at gcc dot gnu.org 2011-05-20 17:20 ` 3dw4rd at verizon dot net 2011-05-20 20:05 ` tristan.wibberley at gmail dot com 2011-09-27 15:35 ` dodji at gcc dot gnu.org 2011-10-02 21:46 ` jason at gcc dot gnu.org [this message] 2011-10-02 21:53 ` jason at gcc dot gnu.org 2011-10-14 19:17 ` jason at gcc dot gnu.org 2012-04-16 2:12 ` jason at gcc dot gnu.org 2008-03-27 17:32 [Bug c++/35722] New: " dgregor at gcc dot gnu dot org 2008-03-27 17:32 ` [Bug c++/35722] " dgregor at gcc dot gnu dot org 2008-12-02 17:51 ` jason at gcc dot gnu dot org 2009-01-06 19:47 ` jason at gcc dot gnu dot org 2009-01-07 0:06 ` jason at gcc dot gnu dot org 2009-04-04 23:12 ` sebor at roguewave dot com 2009-04-05 4:20 ` jason at gcc dot gnu dot org 2009-04-05 14:20 ` sebor at roguewave dot com 2009-04-05 17:12 ` sebor at roguewave dot com 2009-04-05 19:34 ` jason at gcc dot gnu dot org 2009-08-13 5:01 ` jack dot q dot word at gmail dot com 2009-08-13 5:05 ` jack dot q dot word at gmail dot com 2009-08-13 5:06 ` jack dot q dot word at gmail dot com 2009-08-13 5:14 ` jack dot q dot word at gmail dot com 2010-01-22 9:12 ` chris at bubblescope dot net
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-35722-4-E5AYEYWLNv@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).