public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38174] Missing some built-in candidates for operator overloading
Date: Thu, 13 Oct 2011 02:50:00 -0000 [thread overview]
Message-ID: <bug-38174-4-DlspP5TugD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38174-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38174
--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> 2011-10-13 02:49:30 UTC ---
(In reply to comment #3)
> So, for operator== for example, we reach the end of add_builtin_candidate, the
> conditional is true, and we proceed with two calls to build_builtin_candidate
> for pairs of const int* and pairs of volatile int*, I don't see the analysis
> required to figure out that we need also the version for pairs of const
> volatile int*. Should be open coded here?
In the code where we generate those two pairs, if the two pointers have a
composite pointer type, we should instead generate a single candidate with that
type.
next prev parent reply other threads:[~2011-10-13 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-38174-4@http.gcc.gnu.org/bugzilla/>
2011-10-12 21:38 ` paolo.carlini at oracle dot com
2011-10-12 21:41 ` paolo.carlini at oracle dot com
2011-10-12 22:14 ` paolo.carlini at oracle dot com
2011-10-13 2:50 ` jason at gcc dot gnu.org [this message]
2011-10-13 9:39 ` paolo.carlini at oracle dot com
2011-10-13 14:27 ` jason at redhat dot com
2011-10-14 0:20 ` paolo.carlini at oracle dot com
2011-10-14 1:43 ` paolo.carlini at oracle dot com
2011-10-14 14:43 ` paolo at gcc dot gnu.org
2011-10-14 14:45 ` paolo.carlini at oracle dot com
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-38174-4-DlspP5TugD@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).