public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
To: C.vanReeuwijk@twi.tudelft.nl
Cc: egcs-bugs@cygnus.com, frits@pgsultra.twi.tudelft.nl, leo@lspace.org
Subject: Re: Bug report: internal compiler error
Date: Sat, 11 Jul 1998 07:27:00 -0000	[thread overview]
Message-ID: <199807111426.QAA00153@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: <19980710143118.B14340@pds.twi.tudelft.nl>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

> I have reported the same ICE before (early april), but I've managed
> to reduce the example (in fact, I've *halved* the line count :-)).

Thanks for your test case, I'll add it as g++.pt/explicit69.C.
A patch for the bug is below.

Martin

1998-07-11  Martin von Löwis  <loewis@informatik.hu-berlin.de>

	* semantics.c (finish_class_definition): Gracefully handle
	classes that look like template instantiations.

Index: semantics.c
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/cp/semantics.c,v
retrieving revision 1.14
diff -c -p -r1.14 semantics.c
*** semantics.c	1998/07/07 11:25:01	1.14
--- semantics.c	1998/07/11 08:25:40
*************** finish_class_definition (t, components, 
*** 1293,1298 ****
--- 1298,1309 ----
       etc.  */
    shadow_tag (CLASSTYPE_AS_LIST (t)); */
  #endif
+ 
+   if (processing_explicit_instantiation)
+     {
+       /* We got 'template class x {};'. We will complain later. */
+       return t;
+     }
  
    /* finish_struct nukes this anyway; if finish_exception does too,
       then it can go.  */


  reply	other threads:[~1998-07-11  7:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-10  5:31 C. van Reeuwijk
1998-07-11  7:27 ` Martin von Loewis [this message]
1998-08-22  1:58 Bug Report: Internal Compiler Error Ramon Fernandez
1998-08-22  8:54 ` Martin von Loewis
1999-05-31 21:06 Bug report: internal compiler error Sascha Schumann
1999-06-17 11:09 Bug Report: Internal Compiler Error Bill Wendling
1999-06-30 23:07 ` Martin v. Loewis
1999-10-31 23:03 BUG REPORT: internal compiler error Steve Madsen
1999-10-08  4:23 ` Gerald Pfeifer
     [not found] <Pine.HPX.4.21.0004272125500.1168-101000@verdande.diku.dk>
2000-04-27 13:33 ` bug report: Internal " Martin v. Loewis
2000-09-14  1:16 BUG REPORT: Internal Compiler error Thomas Hendel
2001-06-13 19:05 bug report: Internal compiler error Rob Kaper
2006-11-03 15:05 BUG report : " R.J.Sivakumar

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=199807111426.QAA00153@mira.isdn.cs.tu-berlin.de \
    --to=martin@mira.isdn.cs.tu-berlin.de \
    --cc=C.vanReeuwijk@twi.tudelft.nl \
    --cc=egcs-bugs@cygnus.com \
    --cc=frits@pgsultra.twi.tudelft.nl \
    --cc=leo@lspace.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).