public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pl.smith.mail at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56377] [4.8 Regression] <missing> template args in substitution-failure diagnostics
Date: Mon, 18 Feb 2013 16:12:00 -0000	[thread overview]
Message-ID: <bug-56377-4-m07wYptVuG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56377-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Paul Smith <pl.smith.mail at gmail dot com> 2013-02-18 16:12:00 UTC ---
Looks like this was introduced in rev. 190664, with the merging of
'deduction_tsubst_fntype' into 'fn_type_unification'.

The instantiation context is constructed with 'targs' as the vector of template
arguments, which is still empty when substituting the explicit arguments into
the function type the first time. This can be fixed by either constructing the
instantiation context using 'explicit_targs' when non-null, or by copying
'explicit_targs' into 'targs' before the substitution.


  reply	other threads:[~2013-02-18 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 16:05 [Bug c++/56377] New: " pl.smith.mail at gmail dot com
2013-02-18 16:12 ` pl.smith.mail at gmail dot com [this message]
2013-02-18 16:16 ` [Bug c++/56377] " paolo.carlini at oracle dot com
2013-02-19  9:33 ` rguenth at gcc dot gnu.org
2013-02-19  9:58 ` jakub at gcc dot gnu.org
2013-02-20 14:52 ` rguenth at gcc dot gnu.org
2013-02-22 15:58 ` jason at gcc dot gnu.org
2013-02-22 22:25 ` jason at gcc dot gnu.org
2013-02-23  1:59 ` jason at gcc dot gnu.org
2013-02-23 15:16 ` pl.smith.mail at gmail dot com
2013-02-26  4:28 ` jason at gcc dot gnu.org
2013-02-26  4:29 ` 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-56377-4-m07wYptVuG@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).