public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10661
Date: Thu, 08 May 2003 18:56:00 -0000 [thread overview]
Message-ID: <20030508185600.6707.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/10661; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Jason Merrill <jason@redhat.com>
Cc: Giovanni Bajo <giovannibajo@libero.it>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/10661
Date: Thu, 8 May 2003 13:51:50 -0500 (CDT)
> Hmm, the analysis in the PR is correct; the testcase is ill-formed. My
> patch will make it work, but probably isn't worth applying; I don't think
> well-formed code will have the same problem.
I would appreciate some patch nevertheless: the testcase presently just
ICEs, without any prior error message. Whether you make the testcase
compile properly or reject it with an error, I don't care, but anything
should be better than just an ICE!
Giovanni: you asked about tests with older compilers -- your testcase ICEs
every compiler from 2.95 to 3.3. It works with 3.4, i.e. we get a proper
error message. Fixing the issue with the missing "template" allows
compilers since 3.0 to succeed, 2.95 still ICEs.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-08 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 18:56 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 22:36 c++/10661 jason
2003-05-08 14:56 c++/10661 Wolfgang Bangerth
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=20030508185600.6707.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--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).