public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20293] [3.4/4.0/4.1 regression] Wrong diagnostic for ambiguous access Date: Mon, 31 Oct 2005 02:49:00 -0000 [thread overview] Message-ID: <20051031024929.14731.qmail@sourceware.org> (raw) In-Reply-To: <bug-20293-6594@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from mmitchel at gcc dot gnu dot org 2005-10-31 02:49 ------- Leaving as P2; we should try to fix this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20293
next parent reply other threads:[~2005-10-31 2:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20293-6594@http.gcc.gnu.org/bugzilla/> 2005-10-31 2:49 ` mmitchel at gcc dot gnu dot org [this message] 2005-11-14 1:32 ` mmitchel at gcc dot gnu dot org 2005-11-14 1:45 ` mmitchel at gcc dot gnu dot org 2005-11-14 1:50 ` [Bug c++/20293] [3.4/4.0 " mmitchel at gcc dot gnu dot org 2006-03-11 3:17 ` mmitchel at gcc dot gnu dot org 2007-01-18 3:39 ` [Bug c++/20293] [4.0 " gdr at gcc dot gnu dot org 2005-03-02 22:19 [Bug c++/20293] New: namespace name lost igodard at pacbell dot net 2005-03-02 23:03 ` [Bug c++/20293] [3.4/4.0/4.1 regression] Wrong diagnostic for ambiguous access bangerth at dealii dot org 2005-03-02 23:24 ` giovannibajo at libero dot it 2005-03-08 2:31 ` pinskia at gcc dot gnu dot org 2005-03-11 16:27 ` lerdsuwa at gcc dot gnu dot org 2005-05-19 17:35 ` mmitchel at gcc dot gnu dot org 2005-07-22 21:17 ` pinskia at gcc dot gnu dot org 2005-09-11 1:51 ` bangerth at dealii dot org 2005-09-27 16:13 ` mmitchel 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=20051031024929.14731.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).