public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, reichelt@igpm.rwth-aachen.de Subject: Re: c++/5975: ICE with typedefs and templates Date: Tue, 20 May 2003 20:57:00 -0000 [thread overview] Message-ID: <20030520205753.23699.qmail@sources.redhat.com> (raw) Old Synopsis: [3.3 regression] ICE with typedefs and templates New Synopsis: ICE with typedefs and templates State-Changed-From-To: analyzed->closed State-Changed-By: reichelt State-Changed-When: Tue May 20 20:57:52 2003 State-Changed-Why: Oops. It's not a regression. gcc 3.0.x is just "confused by earlier errors, bailing out". Even gcc 2.95.x has tree checking failures. So I close the PR as fixed on mainline. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5975
next reply other threads:[~2003-05-20 20:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-20 20:57 reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-13 3:45 lerdsuwa 2002-07-11 8:13 lerdsuwa 2002-06-10 8:53 rodrigc 2002-06-10 6:16 Reichelt 2002-05-11 9:57 rodrigc 2002-04-10 7:56 Reichelt 2002-03-15 7:16 reichelt
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=20030520205753.23699.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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: linkBe 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).