public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH,c++] describe reasons for function template overload resolution failure
Date: Sat, 28 May 2011 14:03:00 -0000	[thread overview]
Message-ID: <4DE05611.1050806@redhat.com> (raw)
In-Reply-To: <20110527202237.GA851@nightcrawler>

On 05/27/2011 04:22 PM, Nathan Froyd wrote:
> +         /* The PARM is not one we're trying to unify.  Just check
> +            to see if it matches ARG.  */
> +         int result = !(TREE_CODE (arg) == TREE_CODE (parm)
> +                        && cp_tree_equal (parm, arg));
> +         if (result)
> +           unify_template_parameter_mismatch (explain_p, parm, tparm);

This should be unify_template_argument_mismatch (explain_p, parm, arg);

So we can drop unify_template_parameter_mismatch.

OK with that change.

Jason

  reply	other threads:[~2011-05-28  1:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  6:36 Nathan Froyd
2011-05-10 23:29 ` Jason Merrill
2011-05-16 20:28   ` Nathan Froyd
2011-05-18 18:36     ` Jason Merrill
2011-05-18 20:04       ` Nathan Froyd
2011-05-18 20:34         ` Jason Merrill
2011-05-25 19:40           ` Nathan Froyd
2011-05-26 16:52             ` Jason Merrill
2011-05-26 20:53               ` Nathan Froyd
2011-05-27 20:23                 ` Jason Merrill
2011-05-28  0:44                   ` Nathan Froyd
2011-05-28 14:03                     ` Jason Merrill [this message]
2011-07-17  7:56                       ` Jason Merrill
  -- strict thread matches above, loose matches on Subject: below --
2011-02-02 21:05 Nathan Froyd
2011-02-15  3:34 ` Mark Mitchell

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=4DE05611.1050806@redhat.com \
    --to=jason@redhat.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@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).