public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: anene@cup.hp.com
To: gcc-gnats@gcc.gnu.org
Cc: atrick@cup.hp.com
Subject: c++/2861: Parser crashes while parsing a call a template function using the template keyword
Date: Thu, 17 May 2001 21:26:00 -0000	[thread overview]
Message-ID: <20010518042215.21233.qmail@sourceware.cygnus.com> (raw)

>Number:         2861
>Category:       c++
>Synopsis:       Parser crashes while parsing a call a template function using the template keyword
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu May 17 21:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Amitabh Nene
>Release:        gcc version 3.0 20010516 (prerelease)
>Organization:
>Environment:
Linux 2.2.16-22enterprise #1 SMP Tue Aug 22 16:29:32 EDT 2000 i686 unknown
>Description:
g++bug.cpp: In function `int main()':
g++bug.cpp:10: Internal error #980519.
g++bug.cpp:10: Internal compiler error in build_member_call, at cp/init.c:1523
Please submit a full bug report, with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
>How-To-Repeat:
namespace Foo
{
    template<typename _T>
    void test() {
    }
}

int main()
{
    Foo::template test<int>();
}
>Fix:
Workaround is to use Foo::test<int>(), instead of 
Foo::template test<int>

However the other proprietary compiler I am using ALWAYS needs
the template keyword, hence its a severe bug for me from a code
management perspective (last thing i want is #ifdefs)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-17 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-17 21:26 anene [this message]
2003-01-01 13:38 neroden

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=20010518042215.21233.qmail@sourceware.cygnus.com \
    --to=anene@cup.hp.com \
    --cc=atrick@cup.hp.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).