public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46831] [4.6 Regression][C++0x] Crash when it tries to do an invalid ICS with a conversion function template
Date: Thu, 27 Jan 2011 13:42:00 -0000 [thread overview]
Message-ID: <bug-46831-4-FORlChemGr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46831-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46831
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> 2011-01-27 13:09:52 UTC ---
(In reply to comment #1)
>
> --------------------------------------------------
> We can make this to crash on valid code, too:
> --------
>
> struct B { };
> struct D : B { };
> struct A {
> template<typename T = void> operator D&();
> operator long();
> };
>
> void f(long);
> void f(B&);
>
> int main() { f(A()); }
This ICE is also caused by revision 159335:
http://gcc.gnu.org/ml/gcc-cvs/2010-05/msg00387.html
next prev parent reply other threads:[~2011-01-27 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 3:21 [Bug c++/46831] New: " schaub-johannes at web dot de
2010-12-07 4:09 ` [Bug c++/46831] [C++0x] " schaub.johannes at googlemail dot com
2010-12-07 10:59 ` paolo.carlini at oracle dot com
2010-12-07 11:22 ` rguenth at gcc dot gnu.org
2010-12-07 15:37 ` redi at gcc dot gnu.org
2010-12-27 19:48 ` [Bug c++/46831] [4.6 Regression][C++0x] " jakub at gcc dot gnu.org
2011-01-21 9:30 ` jakub at gcc dot gnu.org
2011-01-27 13:25 ` hjl.tools at gmail dot com
2011-01-27 13:42 ` hjl.tools at gmail dot com [this message]
2011-02-21 0:11 ` jason at gcc dot gnu.org
2011-02-21 2:12 ` jason at gcc dot gnu.org
2011-02-21 17:24 ` 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-46831-4-FORlChemGr@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).