public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/35112] [4.2/4.3/4.4 regression] ICE and broken diagnostic with ambiguous class name Date: Fri, 04 Jul 2008 22:33:00 -0000 [thread overview] Message-ID: <20080704223302.17421.qmail@sourceware.org> (raw) In-Reply-To: <bug-35112-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jsm28 at gcc dot gnu dot org 2008-07-04 22:33 ------- Closing 4.1 branch. -- jsm28 at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.1/4.2/4.3/4.4 regression]|[4.2/4.3/4.4 regression] ICE |ICE and broken diagnostic |and broken diagnostic with |with ambiguous class name |ambiguous class name Target Milestone|4.1.3 |4.2.5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35112
next prev parent reply other threads:[~2008-07-04 22:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-06 20:12 [Bug c++/35112] New: [4.1/4.2/4.3 " reichelt at gcc dot gnu dot org 2008-02-06 20:12 ` [Bug c++/35112] " reichelt at gcc dot gnu dot org 2008-02-06 20:44 ` jakub at gcc dot gnu dot org 2008-02-06 20:44 ` rguenth at gcc dot gnu dot org 2008-02-06 20:45 ` rguenth at gcc dot gnu dot org 2008-07-04 22:33 ` jsm28 at gcc dot gnu dot org [this message] 2009-03-31 20:19 ` [Bug c++/35112] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:46 ` rguenth at gcc dot gnu dot org 2009-11-26 20:45 ` paolo dot carlini at oracle dot com 2009-11-27 10:45 ` paolo at gcc dot gnu dot org 2009-11-27 10:46 ` [Bug c++/35112] [4.3/4.4 " paolo dot carlini at oracle dot com 2010-04-06 11:23 ` rguenth at gcc dot gnu dot org 2010-04-06 11:54 ` redi at gcc dot gnu dot org 2010-07-31 9:32 ` rguenth at gcc dot gnu dot org
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=20080704223302.17421.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).