public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jototland@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/6289: partial template specialization and friend
Date: Sat, 13 Apr 2002 15:06:00 -0000	[thread overview]
Message-ID: <20020413220138.8679.qmail@sources.redhat.com> (raw)


>Number:         6289
>Category:       c++
>Synopsis:       partial template specialization and friend
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 13 15:06:09 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Jo Totland
>Release:        g++ 3.0.4, g++ 2.95.4
>Organization:
>Environment:
Debian testing distribution, self-compiled linux kernel version 2.4.18
>Description:
While doing something tricky with templates I got an internal compiler error.

jo@bogon:~/units$ g++-3.0 -ansi -Wall -c minimal.cc
minimal.cc:15: warning: `class my_frobnicator' declares a new type at namespace 
   scope;
   to refer to the inherited type, say `class foo::type'
   (names from dependent base classes are not visible to unqualified name 
   lookup)
minimal.cc:17: Internal compiler error in pop_binding, at cp/decl.c:1186
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

A minimal test program that triggers the bug is included.
>How-To-Repeat:
recompile the included test-program
>Fix:
no idea
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="minimal.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="minimal.cc"

dGVtcGxhdGUgPHR5cGVuYW1lIEE+IGNsYXNzIGZvbzsKCnN0cnVjdCBiYXIge307CgpzdHJ1Y3Qg
YmFyX2Zyb2JuaWNhdG9yIHt9OwoKdGVtcGxhdGUgPHR5cGVuYW1lIEE+CmNsYXNzIHdoaWNoX2Zy
b2JuaWNhdG9yOwp0ZW1wbGF0ZSA8PiBjbGFzcyB3aGljaF9mcm9ibmljYXRvcjxiYXI+IHsgdHlw
ZWRlZiBiYXJfZnJvYm5pY2F0b3IgdHlwZTsgfTsKCnRlbXBsYXRlIDx0eXBlbmFtZSBBPgpjbGFz
cyBmb28KewogIHR5cGVkZWYgdHlwZW5hbWUgd2hpY2hfZnJvYm5pY2F0b3I8QT46OnR5cGUgbXlf
ZnJvYm5pY2F0b3I7CiAgZnJpZW5kIGNsYXNzIG15X2Zyb2JuaWNhdG9yOwp9Cg==


             reply	other threads:[~2002-04-13 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 15:06 jototland [this message]
2002-05-07 15:16 Reichelt
2002-05-08  1:46 Wolfgang Bangerth
2002-05-08  3:26 Reichelt
2002-05-08  4:46 Nathan Sidwell
2002-05-14  8:10 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=20020413220138.8679.qmail@sources.redhat.com \
    --to=jototland@hotmail.com \
    --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).