public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19143] New: [4.0 regression] ICE on invalid template parameter Date: Fri, 24 Dec 2004 01:39:00 -0000 [thread overview] Message-ID: <20041224013907.19143.reichelt@gcc.gnu.org> (raw) The following invalid code snippet triggers an ICE on mainline: ============================================== template<int> struct A; template<> struct A<template> {}; ============================================== bug.cc:2: error: missing '>' to terminate the template argument list bug.cc:2: error: template argument 1 is invalid bug.cc:2: error: missing '>' to terminate the template argument list bug.cc:2: error: template argument 1 is invalid bug.cc:2: error: 'A' is not a template bug.cc:2: error: missing '>' to terminate the template argument list bug.cc:2: internal compiler error: Segmentation fault Please submit a full bug report, [etc.] Alexandre, this was causes by your path for PR18757: http://gcc.gnu.org/ml/gcc-cvs/2004-12/msg00382.html Could you please have a look? -- Summary: [4.0 regression] ICE on invalid template parameter Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, error-recovery, monitored Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org CC: aoliva at gcc dot gnu dot org,gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19143
next reply other threads:[~2004-12-24 1:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-24 1:39 reichelt at gcc dot gnu dot org [this message] 2004-12-24 2:16 ` [Bug c++/19143] " pinskia at gcc dot gnu dot org 2004-12-29 8:05 ` aoliva at redhat dot com 2005-01-29 2:03 ` mmitchel at gcc dot gnu dot org
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=20041224013907.19143.reichelt@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).