public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21799] [4.0/4.1 regression] Spurious ambiguity with pointers to members
Date: Thu, 23 Jun 2005 15:04:00 -0000 [thread overview]
Message-ID: <20050623150415.18758.qmail@sourceware.org> (raw)
In-Reply-To: <20050528163432.21799.bangerth@dealii.org>
------- Additional Comments From mark at codesourcery dot com 2005-06-23 15:04 -------
Subject: Re: [4.0/4.1 regression] Spurious ambiguity with
pointers to members
bangerth at dealii dot org wrote:
> ------- Additional Comments From bangerth at dealii dot org 2005-06-23 14:51 -------
> Mark, since you are looking for bugs to be fixed in 4.0.1 again, would
> this regression between 4.0.0 and the present state of 4.0.1 interest
> you? This is code that also appears in boost...
Definitely a serious bug, but I'm not sure I want to try to fix it
before 4.0.1. I'm really trying to confine myself to wrong-code bugs on
primary platforms...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21799
next prev parent reply other threads:[~2005-06-23 15:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 16:35 [Bug c++/21799] New: [4.1 " bangerth at dealii dot org
2005-05-28 17:43 ` [Bug c++/21799] " bangerth at dealii dot org
2005-05-28 17:59 ` pinskia at gcc dot gnu dot org
2005-05-31 13:52 ` bangerth at dealii dot org
2005-05-31 14:05 ` bangerth at dealii dot org
2005-05-31 17:26 ` pinskia at gcc dot gnu dot org
2005-05-31 17:56 ` bangerth at dealii dot org
2005-06-20 21:30 ` bangerth at dealii dot org
2005-06-21 0:19 ` giovannibajo at libero dot it
2005-06-21 15:55 ` bangerth at dealii dot org
2005-06-21 16:00 ` bangerth at dealii dot org
2005-06-21 16:02 ` [Bug c++/21799] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-06-21 16:07 ` pinskia at gcc dot gnu dot org
2005-06-21 16:15 ` bangerth at dealii dot org
2005-06-21 20:43 ` bangerth at ices dot utexas dot edu
2005-06-21 20:45 ` Andrew Pinski
2005-06-21 20:45 ` pinskia at physics dot uc dot edu
2005-06-21 20:58 ` bangerth at dealii dot org
2005-06-22 1:24 ` giovannibajo at libero dot it
2005-06-23 14:51 ` bangerth at dealii dot org
2005-06-23 15:04 ` mark at codesourcery dot com [this message]
2005-06-23 15:08 ` bangerth at ices dot utexas dot edu
2005-06-23 15:20 ` mark at codesourcery dot com
2005-06-24 13:37 ` nathan at gcc dot gnu dot org
2005-06-24 15:53 ` nathan at gcc dot gnu dot org
2005-06-24 16:03 ` bangerth at ices dot utexas dot edu
2005-06-24 16:14 ` bangerth at ices dot utexas dot edu
2005-06-26 0:45 ` mark at codesourcery dot com
2005-07-06 17:02 ` mmitchel at gcc dot gnu dot org
2005-07-08 11:06 ` cvs-commit at gcc dot gnu dot org
2005-07-08 11:08 ` nathan at gcc dot gnu dot org
2005-07-11 11:02 ` reichelt at gcc dot gnu dot org
2005-08-12 9:24 ` [Bug c++/21799] [4.0 " cvs-commit at gcc dot gnu dot org
2005-08-12 9:36 ` nathan at gcc dot gnu dot org
2005-08-12 9:41 ` cvs-commit 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=20050623150415.18758.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: 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).