public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45012] Invalid ambiguity on partial class specialization matching
Date: Thu, 17 Nov 2011 16:11:00 -0000	[thread overview]
Message-ID: <bug-45012-4-sTPqCYIuL9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45012-4@http.gcc.gnu.org/bugzilla/>

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

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ramana at gcc dot gnu.org

--- Comment #6 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2011-11-17 16:03:34 UTC ---
It was fixed actually by this commit . 

Author: jason
Date: Tue Sep 27 02:13:00 2011
New Revision: 179230

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179230
Log:
    PR c++/45102
    * pt.c (tsubst_copy_and_build) [CONST_DECL]: Don't pull out
    constant value if we're still in a template.

Added:
    trunk/gcc/testsuite/g++.dg/template/partial13.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/pt.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-11-17 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45012-4@http.gcc.gnu.org/bugzilla/>
2011-09-26 18:31 ` paolo.carlini at oracle dot com
2011-09-27  2:40 ` jason at gcc dot gnu.org
2011-11-17 16:11 ` ramana at gcc dot gnu.org [this message]
2010-07-21  2:43 [Bug c++/45012] New: " rodolfo at rodsoft dot org
2010-07-21  2:49 ` [Bug c++/45012] " rodolfo at rodsoft dot org
2010-07-21  2:54 ` pinskia at gmail dot com
2010-07-21  3:03 ` rodolfo at rodsoft dot 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-45012-4-sTPqCYIuL9@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).