public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46394] [C++0X] [4.6 Regression] no matching function with default template parameter
Date: Tue, 04 Jan 2011 15:33:00 -0000	[thread overview]
Message-ID: <bug-46394-4-rU94FLqQkZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46394-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46394

--- Comment #4 from Dodji Seketeli <dodji at gcc dot gnu.org> 2011-01-04 15:32:53 UTC ---
I think what's happening is, at some point during template parameters
fixup (to build proper canonical types for dependent parms) we try to
substitute the U template parameter pack [and the the remaining unamed
template parm] into the pattern of the default argument
std::remote_reference<U>::type... . The TYPENAME_TYPE case of tsubst then
logically calls tsubst_aggr_type on 'std::remote_reference<U>'. That
later function in turn calls lookup_template_class with
std::remote_reference as argument to D1 and a TYPE_PACK_EXPANSION
built for the template parameter U (by template_parm_to_arg) and
argument to ARGLIST.

At that point we are trying to match a template argument which is
a pack expansion with a template parameter that is not a
parameter pack - and we hit
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35722.

So I think I am going to focus on that bug and see.


  parent reply	other threads:[~2011-01-04 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 14:41 [Bug c++/46394] New: [C++0X] no matching function with default template argument marc.glisse at normalesup dot org
2010-11-09 14:58 ` [Bug c++/46394] [C++0X] [4.6 Regression] no matching function with default template parameter paolo.carlini at oracle dot com
2010-11-09 15:06 ` paolo.carlini at oracle dot com
2010-12-17 20:04 ` marc.glisse at normalesup dot org
2010-12-17 20:10 ` hjl.tools at gmail dot com
2011-01-03 20:20 ` dodji at gcc dot gnu.org
2011-01-04 15:33 ` dodji at gcc dot gnu.org [this message]
2011-02-04 19:53 ` dodji at gcc dot gnu.org
2011-02-08 13:45 ` rguenth at gcc dot gnu.org
2011-02-20 17:42 ` dodji at gcc dot gnu.org
2011-02-20 18:09 ` dodji at gcc dot gnu.org
2011-02-20 18:10 ` dodji 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-46394-4-rU94FLqQkZ@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: link
Be 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).