public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for c++/35255 (address of template-id)
Date: Fri, 24 Jun 2011 13:12:00 -0000	[thread overview]
Message-ID: <BANLkTimScz-rVgR97Xp1cOUGVO2A0T2mSg@mail.gmail.com> (raw)
In-Reply-To: <4E03F22C.9040208@redhat.com>

On Thu, Jun 23, 2011 at 22:10, Jason Merrill <jason@redhat.com> wrote:
> Per DR 115, if the context of a template-id doesn't give enough type
> information to resolve it and the template-id fully resolves exactly one
> specialization, we should use that one.  The code in
> resolve_overloaded_unification was trying to do this, but was failing to
> handle the case where there are additional templates that aren't fully
> resolved.
>
> Tested x86_64-pc-linux-gnu, applying to trunk.

Patch missing.

  reply	other threads:[~2011-06-24 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  2:44 Jason Merrill
2011-06-24 13:12 ` Diego Novillo [this message]
2011-06-24 22:21   ` Jason Merrill

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=BANLkTimScz-rVgR97Xp1cOUGVO2A0T2mSg@mail.gmail.com \
    --to=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    /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).