public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fang@csl.cornell.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/7446: gcc 2.95.3 internal compiler error on compiling "ice.ii"
Date: Tue, 30 Jul 2002 11:56:00 -0000	[thread overview]
Message-ID: <20020730185254.17799.qmail@sources.redhat.com> (raw)


>Number:         7446
>Category:       c++
>Synopsis:       gcc 2.95.3 internal compiler error on compiling "ice.ii"
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 30 11:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     fang@csl.cornell.edu
>Release:        gcc version 2.95.3 [FreeBSD] 20010315 (release)
>Organization:
>Environment:
FreeBSD 4.3-RELEASE #15: Tue Aug 28 16:54:58 EDT 2001  i386
>Description:
internal compiler error reported on compiling "ice.ii"

output:
In file included from ice.cc:4:
ice.h:41: Internal compiler error.
ice.h:41: Please submit a full bug report.
ice.h:41: See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions.

should report some error about misuse of template?
>How-To-Repeat:
gcc ice.ii
>Fix:
a work around:
in "ice.ii", change in class declaration and uses:
AT<T>::BT
to:
AT<T>::BT<T>

not sure if this adheres to C++ standard... 
but at least gcc doesn't report any errors after this change
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="ice.ii"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ice.ii"

IyAxICJpY2UuY2MiCiAKIAoKIyAxICJpY2UuaCIgMQogCiAKIAogCiAKIAogCgogCiAKIAoKCgpj
bGFzcyBBIHsKcHVibGljOgoJY2xhc3MgQjsKcHJvdGVjdGVkOgoJQiogYjsKfTsKCmNsYXNzIEE6
OkIgewpwdWJsaWM6CglBOjpCKiBuZXh0OwpwdWJsaWM6CglCKEE6OkIqIG4gPSAwICkgeyBuZXh0
ID0gbjsgfQkJCSAKCXZpcnR1YWwgfkIoKSB7IGlmIChuZXh0ICE9IDAgKSBkZWxldGUgbmV4dDsg
fQkgCgp9OwoKdGVtcGxhdGUgPGNsYXNzIFQ+CmNsYXNzIEFUIDogcHVibGljIEEgewpwdWJsaWM6
CgljbGFzcyBCVDsKcHJvdGVjdGVkOgoJQlQqIGZpcnN0OwoKfTsKCnRlbXBsYXRlIDxjbGFzcyBU
PgpjbGFzcyBBVDxUPjo6QlQgOiBwdWJsaWMgQTo6QiB7CQkgCnB1YmxpYzoKCUFUPFQ+OjpCVCog
bmV4dDsKCVQgdmFsOwoKcHVibGljOgoJQlQoQVQ8VD46OkJUKiBuID0gMCApOwoJQlQoY29uc3Qg
VCYgdiwgQVQ8VD46OkJUKiBuID0gMCApOwoJdmlydHVhbCB+QlQoKTsKfTsKCiMgNCAiaWNlLmNj
IiAyCgogCgppbnQgbWFpbihpbnQgYXJnYywgY2hhciogYXJndltdKSB7CgkgCglyZXR1cm4gMDsK
fQo=


             reply	other threads:[~2002-07-30 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 11:56 fang [this message]
2002-07-30 12:50 paolo

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=20020730185254.17799.qmail@sources.redhat.com \
    --to=fang@csl.cornell.edu \
    --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).