public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: benko@sztaki.hu
To: gcc-gnats@gcc.gnu.org
Subject: c++/5004: Full specialisation of member templates failing
Date: Tue, 04 Dec 2001 01:36:00 -0000	[thread overview]
Message-ID: <20011204092913.20347.qmail@sources.redhat.com> (raw)


>Number:         5004
>Category:       c++
>Synopsis:       Full specialisation of member templates failing
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 04 01:36:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Benko Pal
>Release:        3.0.2
>Organization:
>Environment:
SuSE linux 7.1, i686
>Description:
The attached program tries to specialise a member class
template in (hopefully) all possible ways.  Partial
specialisations succeed, but full specialisation succeeds
only when the enclosing class is non-templated, and the
specialisation is declared outside of the enclosing class.

arta:~/c/proba$ /gml/shared/gcc-3.0.2/bin/g++ -c spectemplmem.cc
spectemplmem.cc:12: explicit specialization in non-namespace scope `struct 
   a<T>'
spectemplmem.cc:12: enclosing class templates are not explicitly specialized
spectemplmem.cc:14: template parameters not used in partial specialization:
spectemplmem.cc:14:         `T'
spectemplmem.cc:24: enclosing class templates are not explicitly specialized
spectemplmem.cc:26: template parameters not used in partial specialization:
spectemplmem.cc:26:         `T'
spectemplmem.cc:38: explicit specialization in non-namespace scope `struct c'
zsh: exit 1     /gml/shared/gcc-3.0.2/bin/g++ -c spectemplmem.cc
arta:~/c/proba$ 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="spectemplmem.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="spectemplmem.cc"

dGVtcGxhdGUgPHR5cGVuYW1lIFQ+CnN0cnVjdCBhCnsKICB0ZW1wbGF0ZSA8dHlwZW5hbWUgVT4K
ICBzdHJ1Y3QgYgogIHt9OwoKICB0ZW1wbGF0ZSA8dHlwZW5hbWUgVz4KICBzdHJ1Y3QgYjxiPFc+
ID4KICB7fTsKCiAgdGVtcGxhdGUgPD4KICBzdHJ1Y3QgYjx2b2lkPiAKICB7fTsKfTsKCnRlbXBs
YXRlIDx0eXBlbmFtZSBUPgp0ZW1wbGF0ZSA8dHlwZW5hbWUgVj4Kc3RydWN0IGE8VD46OmI8YTxW
PiA+Cnt9OwoKCnRlbXBsYXRlIDx0eXBlbmFtZSBUPgp0ZW1wbGF0ZSA8PgpzdHJ1Y3QgYTxUPjo6
YjxpbnQ+Cnt9OwoKc3RydWN0IGMKewogIHRlbXBsYXRlIDx0eXBlbmFtZSBVPgogIHN0cnVjdCBi
CiAge307CgogIHRlbXBsYXRlIDx0eXBlbmFtZSBXPgogIHN0cnVjdCBiPGI8Vz4gPgogIHt9OwoK
ICB0ZW1wbGF0ZSA8PgogIHN0cnVjdCBiPHZvaWQ+IAogIHt9Owp9OwoKdGVtcGxhdGUgPHR5cGVu
YW1lIFY+CnN0cnVjdCBjOjpiPGE8Vj4gPgp7fTsKCgp0ZW1wbGF0ZSA8PgpzdHJ1Y3QgYzo6Yjxp
bnQ+Cnt9OwoKCmludAptYWluKCkKewogIGE8Y2hhciAqPjo6YjxhPGludD4gPiAgICAgICBxMDsK
ICBhPHZvaWQ+OjpiPGludD4gICAgICAgICAgICAgcTE7CiAgYTxpbnQ+OjpiPGE8aW50Pjo6Yjx2
b2lkPiA+IHEyOwogIGE8ZmxvYXQ+OjpiPHZvaWQ+ICAgICAgICAgICBxMzsKICBhPGxvbmc+Ojpi
PGNoYXIgKj4gICAgICAgICAgcTQ7CiAgYzo6YjxhPGZsb2F0PiA+ICAgICAgICAgICAgIHE1Owog
IGM6OmI8dm9pZD4gICAgICAgICAgICAgICAgICBxNjsKICBjOjpiPGM6OmI8YTxpbnQ+ID4gPiAg
ICAgICAgcTc7CiAgYzo6YjxpbnQ+ICAgICAgICAgICAgICAgICAgIHE4OwogIGM6OmI8Y2hhciAq
PiAgICAgICAgICAgICAgICBxOTsKCiAgcmV0dXJuIDA7Cn0K


             reply	other threads:[~2001-12-04  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04  1:36 benko [this message]
2002-05-19  4:28 lerdsuwa

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=20011204092913.20347.qmail@sources.redhat.com \
    --to=benko@sztaki.hu \
    --cc=gcc-gnats@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).