public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9336: [3.3 regression] ICE in cp_line_of, at cp/error.c:2191
Date: Mon, 24 Feb 2003 22:36:00 -0000 [thread overview]
Message-ID: <20030224223600.1951.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9336; it has been noted by GNATS.
From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
gcc-prs@gcc.gnu.org, V.Haisman@sh.cvut.cz
Cc:
Subject: Re: c++/9336: [3.3 regression] ICE in cp_line_of, at cp/error.c:2191
Date: Mon, 24 Feb 2003 14:32:48 -0800
With checking enabled, this started being an ICE with this
patch (yeah, it's not terribly interesting):
2002-01-23 Zack Weinberg <zack@codesourcery.com>
* diagnostic.c (internal_error): Do ICE suppression only
when ENABLE_CHECKING is not defined.
There is no ICE with current mainline or 3.2-branch.
3.3 20030224 (with checking enabled) reports:
9336.C: In function `std::pair<std::string, ASTInfo*> insertident(const
std::string&, ASTInfo*)':
9336.C:15: error: `make_pair' undeclared (first use this function)
9336.C:15: error: (Each undeclared identifier is reported only once for
each
function it appears in.)
Internal compiler error: Error reporting routines re-entered.
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
The original ICE is gone, but I think this new one is covered
by other PRs.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9336
next reply other threads:[~2003-02-24 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 22:36 Janis Johnson [this message]
2003-03-13 18:47 jason
2003-03-13 21:02 jason
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=20030224223600.1951.qmail@sources.redhat.com \
--to=janis187@us.ibm.com \
--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).