public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at seketeli dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45383] [4.5 Regression] Implicit conversion to pointer does no longer automatically generate operator== and operator!=.
Date: Wed, 27 Apr 2011 11:43:00 -0000 [thread overview]
Message-ID: <bug-45383-4-CDcMXliPB7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45383-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45383
--- Comment #12 from dodji at seketeli dot org <dodji at seketeli dot org> 2011-04-27 11:37:43 UTC ---
> Dodji, is there any reason not to apply this fix to 4.5 as well?
I was waiting to see how the initial fix would behave in 4.6 and it felt
below my radar. But then PR c++/46824 hinted for a better fix for this
issue. So I am backporting the revert of PR c++/42260 and the fix of PR
c++/46824 instead.
I have tested it on x86_64-unknown-linux-gnu aginst 4.5
next prev parent reply other threads:[~2011-04-27 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45383-4@http.gcc.gnu.org/bugzilla/>
2010-11-08 13:47 ` [Bug c++/45383] [4.5/4.6 " number.cruncher at ntlworld dot com
2010-11-08 23:11 ` dodji at gcc dot gnu.org
2010-11-11 8:24 ` Dodji Seketeli
2010-11-11 8:24 ` dodji at seketeli dot org
2010-11-29 16:32 ` dodji at gcc dot gnu.org
2010-11-29 17:08 ` dodji at gcc dot gnu.org
2010-12-16 13:25 ` rguenth at gcc dot gnu.org
2011-02-22 16:21 ` [Bug c++/45383] [4.5 " dodji at gcc dot gnu.org
2011-03-11 17:44 ` jason at gcc dot gnu.org
2011-04-18 14:41 ` rguenth at gcc dot gnu.org
2011-04-19 23:50 ` jason at gcc dot gnu.org
2011-04-27 11:43 ` dodji at seketeli dot org [this message]
2011-04-27 12:38 ` dodji at seketeli dot org
2011-04-27 13:21 ` rguenth at gcc dot gnu.org
2011-04-28 15:49 ` rguenth at gcc dot gnu.org
2011-04-28 17:05 ` jason at gcc dot gnu.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=bug-45383-4-CDcMXliPB7@http.gcc.gnu.org/bugzilla/ \
--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).