public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug c++/21799] [4.0/4.1 regression] Spurious ambiguity with pointers to members
Date: Tue, 21 Jun 2005 20:45:00 -0000 [thread overview]
Message-ID: <2fac93fae18aa901bd09ae8023ba3f24@physics.uc.edu> (raw)
In-Reply-To: <20050621204302.21960.qmail@sourceware.org>
On Jun 21, 2005, at 4:43 PM, bangerth at ices dot utexas dot edu wrote:
>
> ------- Additional Comments From bangerth at ices dot utexas dot edu
> 2005-06-21 20:43 -------
> Subject: Re: [4.0/4.1 regression] Spurious ambiguity with pointers to
> members
>
>
>> I think this was exposed by the patch for PR 19203 (aka DR 214),
>> could you
>> double check that, that patch makes sense if it exposes this bug.
>
> It has become impossible to take out Nathan's patch from mainline,
> because the
> code has been worked over again in the meantime. A run through the
> regression
> tester may be the best chance to determine which patch broke this.
It might be easier to try to take it out on the 4.0 branch and easier
to run the
regression tester there, I don't have time to either because I am
looking into
the other bug you filed, the seg fault one.
-- Pinski
next prev parent reply other threads:[~2005-06-21 20:45 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 [this message]
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
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=2fac93fae18aa901bd09ae8023ba3f24@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).