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++/10722: [3.3 regression] ICE (segfault) when specializing with an invalid type
Date: Wed, 14 May 2003 23:26:00 -0000 [thread overview]
Message-ID: <20030514232600.25440.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/10722; it has been noted by GNATS.
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-prs@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>,
<bangerth@dealii.org>,
<nobody@gcc.gnu.org>
Cc:
Subject: Re: c++/10722: [3.3 regression] ICE (segfault) when specializing with an invalid type
Date: Thu, 15 May 2003 01:19:58 +0200
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10722
Let's split this PR. I will shortly open a new PR to track the 3.4 issue, we
keep this one only for the 3.3 reduced snippet. In other words, the bug we
track here is:
---------------------------------------------
template <class P, class Q>
struct pair {};
template <typename T>
struct pair<T, INVALID> {
typedef T first_type;
};
---------------------------------------------
pr10722.cpp:5: error: type/value mismatch at argument 2 in template
parameter list for `template<class P, class Q> struct pair'
pr10722.cpp:5: error: expected a type, got `INVALID'
pr10722.cpp:6: internal compiler error: Segmentation fault
Please submit a full bug report,
This is an ice-on-illegal, 3.3 regression with respect to 2.95 where the
code was not ICE-ing the compiler.
Giovanni Bajo
next reply other threads:[~2003-05-14 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 23:26 Giovanni Bajo [this message]
2003-05-17 8:06 Giovanni Bajo
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=20030514232600.25440.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).