public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lerdsuwa at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18950] specialization of template class with inner template members
Date: Mon, 13 Dec 2004 15:27:00 -0000	[thread overview]
Message-ID: <20041213152711.28541.qmail@sourceware.org> (raw)
In-Reply-To: <20041213094233.18950.boris@buf.com>


------- Additional Comments From lerdsuwa at gcc dot gnu dot org  2004-12-13 15:27 -------
Should be allowed according to 14.7.3/16.  All my GCC versions
fail to compile the testcase (maybe some 3.3.x does) so I can't 
verify that it's a regression.

The problem is some incorrect logic in 'determine_specialization':
it tries to deduce N2 from

  template<> template<class T2,int N2>
    T2 Class<int,1>::function( T2 param )

to match against

  template<class T1,int N1> template<class T2,int N2>
    T2 Class<T1,N1>::function( T2 param );


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
      Known to work|                            |2.95.3 3.0.4 3.2.3 3.4.3
                   |                            |4.0.0
   Last reconfirmed|0000-00-00 00:00:00         |2004-12-13 15:27:08
               date|                            |


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


  reply	other threads:[~2004-12-13 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13  9:42 [Bug c++/18950] New: " boris at buf dot com
2004-12-13 15:27 ` lerdsuwa at gcc dot gnu dot org [this message]
2004-12-13 15:55 ` [Bug c++/18950] " pinskia at gcc dot gnu dot org
2004-12-13 17:36 ` boris at buf dot com
2004-12-13 18:09 ` pinskia at gcc dot gnu dot org
     [not found] <bug-18950-4@http.gcc.gnu.org/bugzilla/>
2014-07-07  8:59 ` paolo.carlini at oracle dot com

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=20041213152711.28541.qmail@sourceware.org \
    --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).