public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@ticam.utexas.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/8999: SegFault after illegal template declaration
Date: Wed, 18 Dec 2002 15:16:00 -0000	[thread overview]
Message-ID: <20021218231259.30374.qmail@sources.redhat.com> (raw)


>Number:         8999
>Category:       c++
>Synopsis:       SegFault after illegal template declaration
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 18 15:16:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
gcc 3.3 CVS of last week
>Description:
While loosing overview of a small template metaprogramming
project, I happened to write something like
--------------------------------
template <typename ST, T> struct X {};

int main () {};
--------------------------------
The second template parameter of X is incorrectly given.

This crashes the compiler:

tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c y.cc
y.cc:1: error: parse error before `>' token
y.cc:3: error: cannot declare `::main' to be a template
y.cc:3: internal compiler error: Segmentation fault
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:

>Fix:
Write correct code.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-12-18 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 15:16 bangerth [this message]
2002-12-19  6:52 lerdsuwa
2003-01-01 15:52 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=20021218231259.30374.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.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).