public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ajl13@bellatlantic.net
To: gcc-gnats@gcc.gnu.org
Cc: a.liguori@wowis.com
Subject: c++/5421: GCC 3.0 Issues ICE on explicit template member function friendship
Date: Thu, 17 Jan 2002 20:06:00 -0000	[thread overview]
Message-ID: <20020118040409.18997.qmail@sources.redhat.com> (raw)


>Number:         5421
>Category:       c++
>Synopsis:       GCC 3.0 Issues ICE on explicit template member function friendship
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 17 20:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Anthony Liguori
>Release:        GCC 3.0.0
>Organization:
>Environment:
Linux 2.4.7-10 #1 i686
AMD Athlon
>Description:
GCC generates an interal compiler error when declaring an explict template member function of class B as a friend of class A.  GCC correctly handles a non-explicit template member function friendship though.  It also correctly handles an explicit template function friendship.
>How-To-Repeat:
The tarball includes a sample 5 line snippet that will reproduce the ICE along with the generated .ii file and then output from the ICE.  It requires no #include files so the .ii is the same as the .C file (I've included the .ii anyway).

The command line used to attempt to compile the snippet is:

$ gcc -v -save-temps -g -c -Wall template_friend.C
>Fix:
There is no workaround other than making the friendship no longer required by making the private members public.  This is obviously not an acceptable workaround though for most cases.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="g++-bug_x_tmplt_frnd.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="g++-bug_x_tmplt_frnd.tgz"

H4sIADWeRzwAA+2WWW/jNhCA/Vr9ioH3JUaqy2dWOQDHVjcGXNuwnW3eBFmmZaIyqZJUnKDof+/I
V+IoRZA23bYovxeSwzl4zFBSZJUmoSLBQlDC5lan9PE4ruM0m/WSg7RetDlus1FyWvWq23KbrVoV
9evVVr0Ezt+wlgKZVKEAKIVMLTl7/EO9t+b/o0glskjBNfwKapcKcBEloZQwvYJ7TucwO6mcw2/n
hvGKwrbTRutt/mwtrj1vdjG92tvhCSsaQfuCMnUF4bnxT29ac0C9qH9KPz7GW/VfdQ/133KcRl7/
DcfV9f8t+AQulF8mQads6Hfh/8HLq+eZSjP1sTHeqP+ak/eP6r9Rrzd0/X8LxiScUxaDTEkksVj5
CuxMCjvhUZjYCZ3ZcRSZeUubZ00zzfssezBjltk1y7E3dkaHswWNM0HmsKZq6YFlR3sRGNOlwCiw
4nOSeCAxXEIMdAv3REjKGaAj431hozR1wExCFpvR6SmY3SD4Mrj9EgSXte3g7i7o+qOx32lP/e5G
5N91/NG0NxxMDhrt617w1R9PUHiJOQrm/d5T58lTPvixNxiOUeQ8iUbtaeem73/1+we53/8hCLCX
MfqAzWbFRxNBkE/tupvpZ+InIZht+SixMi9TLncTg2HQG/R7A39nMZl2O8HNcIK7w/gumD+FSZLP
4OKCyfB23PHRTZRml7R21sTuKoyWlJHdsLtrguCos3OuMkaC/OCfj1PCFM1WqeAoLXwxChJKDVwK
dEaj59cMJ3hzeK0VONkE7uf7tfF8KgaNGRd5KjLOyAPF/TMFcypIpLh4hPKz/KAsSrI5sePTU/O+
Vv7zpsXs+ivOZmH08zoU87LxaTcDZcuyyiBJKKIl5C+NkrAkgnhPKheocvWqChRDvbNMXrMqah5r
7Uc+frX5Yr+wBA/Cem+RRm6aZBLMRSoI5k1EpMQXopgpYP6SUaLAnGN+zUJJXskvM97n+D6dTF5Q
k+/MuY02vh9H2oXNVIzvIr5KaYKLnz3CxuhgUrU+N6G6+aTVXDgZo85NqLZBoGW5GwXz81nFMgqb
8moe9JgigoUJECG48GBC4hVmHP4ZofNFmCXKGCUkPxOZzVZUQQiLDI9hlsWAp8qF+t7I31w4OmPJ
MxERoAsIU5SmgmJcy5gQzLfbcd9bKpV6tr1ery3coMVFbEu+UJi9JL9UG71La6lWyRUsuADKtv+D
uCZp6d80jUaj0Wg0Go1Go9FoNBqNRqPRaP7l/A5k/3xgACgAAA==


                 reply	other threads:[~2002-01-18  4:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020118040409.18997.qmail@sources.redhat.com \
    --to=ajl13@bellatlantic.net \
    --cc=a.liguori@wowis.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).