public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7939: [3.3/3.4 regression] [2003-05-03] ICE on function template specialization
Date: Mon, 05 May 2003 00:56:00 -0000	[thread overview]
Message-ID: <20030505005601.16249.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7939; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<kparz@iastate.edu>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc:  
Subject: Re: c++/7939: [3.3/3.4 regression] [2003-05-03] ICE on function template specialization
Date: Mon, 5 May 2003 02:46:22 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7939
 
 This is a regression from 2.95. Currently, we get the following on mainline
 and 3.3:
 
 pr7939.cpp:2: error: `<anonymous>' has incomplete type
 pr7939.cpp:2: error: invalid use of `void'
 pr7939.cpp:2: error: partial specialization `foo<T, void>' of function
 template
 pr7939.cpp:2: internal compiler error: in comptypes, at cp/typeck.c:913
 Please submit a full bug report,
 
 while we used to get this on 2.95:
 
 pr7939.cpp:2: template-id `foo<T, void>' in declaration of primary template
 
 So, there is actually an improvement on the error message (the parser is
 able to understand that the code is trying to define a partial
 specialization of a function template, which is indeed a great diagnostic),
 but then it ICEs during error recovery. I think the error message could also
 be a little epurated (removing those other lines if possible, especially the
 one with <anonymous> which is really cryptic), and maybe specifying
 explicitally that "partial specialization of function template is not
 allowed by ISO C++".
 
 Giovanni Bajo
 


                 reply	other threads:[~2003-05-05  0:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030505005601.16249.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).