public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hg211@ural2.hszk.bme.hu
To: gcc-gnats@gcc.gnu.org
Subject: c++/7718: 'complex' template instantiation causes internal compiler error (gcc 3.1, gcc 3.2)
Date: Sun, 25 Aug 2002 17:36:00 -0000	[thread overview]
Message-ID: <20020825224842.14410.qmail@sources.redhat.com> (raw)


>Number:         7718
>Category:       c++
>Synopsis:       'complex' template instantiation causes internal compiler error (gcc 3.1, gcc 3.2)
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Aug 25 15:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Herman Geza
>Release:        gcc version 3.2 20020809 (Debian prerelease)
>Organization:
>Environment:
i386/Linux, AMD Athlon
>Description:
If you give a template function as a parameter to a template class, and call this template function in a template class-function (it's hard to describe)
gcc 3.1.1 and gcc 3.2 stops with
't.cpp:19: Internal compiler error in tsubst_decl, at cp/pt.c:5648'

Try the attached simple cpp file.

If the default_initializer template function is a simple non-template function, then the sample compiles.
>How-To-Repeat:
compile the sample with 'g++ t.cpp -c'
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="t.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="t.cpp"

dGVtcGxhdGUgPHR5cGVuYW1lIE9CSkVDVD4Kdm9pZCBkZWZhdWx0X2luaXRpYWxpemVyKGNvbnN0
IE9CSkVDVCAmKSB7IH0KCi8vdm9pZCBkZWZhdWx0X2luaXRpYWxpemVyKGNvbnN0IGludCAmKSB7
IH0KCnRlbXBsYXRlIDx0eXBlbmFtZSBPQkpFQ1QsIHZvaWQgaW5pdF9mdW5jdGlvbihjb25zdCBP
QkpFQ1QgJik+CmNsYXNzIGNDb250YWluZXIgewoJcHVibGljOgoJCXRlbXBsYXRlIDx0eXBlbmFt
ZSBJTklUSUFMSVpFUj4KCQl2b2lkIEFkZChjb25zdCBJTklUSUFMSVpFUiAmaW5pdGlhbGl6ZXIp
IHsKCQkJaW5pdF9mdW5jdGlvbihpbml0aWFsaXplcik7CgkJfQp9OwoKaW50IG1haW4oKSB7Cglj
Q29udGFpbmVyPGludCwgZGVmYXVsdF9pbml0aWFsaXplcjxpbnQ+ID4gYzsKCS8vY0NvbnRhaW5l
cjxpbnQsIGRlZmF1bHRfaW5pdGlhbGl6ZXIgPiBjOwoKCWMuQWRkPGludD4oNDIpOwoKCXJldHVy
biAwOwp9Cg==


             reply	other threads:[~2002-08-25 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 17:36 hg211 [this message]
2002-09-13 14:30 nathan
2002-09-16 12:56 nathan

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=20020825224842.14410.qmail@sources.redhat.com \
    --to=hg211@ural2.hszk.bme.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).