public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gdr@gcc.gnu.org, giovannibajo@libero.it Subject: Re: c++/10771: [3.4 regression] [diagnostic] Unreadable error message for illegal specialization Date: Wed, 14 May 2003 21:18:00 -0000 [thread overview] Message-ID: <20030514211834.14167.qmail@sources.redhat.com> (raw) Synopsis: [3.4 regression] [diagnostic] Unreadable error message for illegal specialization State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Wed May 14 21:18:34 2003 State-Changed-Why: Confirmed. Though it's worse: gcc3.2.3 and 3.3 ICE on this code. 3.4 doesn't any more. But I think that we have other reports about the ICE, so we may keep this PR just for the problem with the diagnostics. Is this right Giovanni? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10771
next reply other threads:[~2003-05-14 21:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 21:18 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 23:06 Giovanni Bajo 2003-05-13 18:15 giovannibajo 2003-05-13 18:07 giovannibajo
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=20030514211834.14167.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@gcc.gnu.org \ --cc=giovannibajo@libero.it \ /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).