public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fabian.bergmark at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49921] [C++0x] Segfault during compilation, decltype and operator->*
Date: Sun, 31 Jul 2011 10:57:00 -0000 [thread overview]
Message-ID: <bug-49921-4-pW5iPfw9zX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49921-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49921
--- Comment #2 from fabian.bergmark at gmail dot com 2011-07-31 10:57:17 UTC ---
(In reply to comment #1)
> Confirmed. Mainline says:
>
> 49921.C: In function ‘int main()’:
> 49921.C:15:25: internal compiler error: tree check: expected record_type or
> union_type or qual_union_type, have translation_unit_decl in
> maybe_dummy_object, at cp/tree.c:2474
To quote Modern C++ Design by Andrei Alexandrescu:
"In C++, where every object has a type, the result of operator->* or operator.*
is a unique exception."
and
"Both are binary functions all right, and they return something to which you
can apply the function-call operator immediately, but that "something" does no
have a type."
Is this possibly the reason to the error?
next prev parent reply other threads:[~2011-07-31 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 10:03 [Bug c++/49921] New: " fabian.bergmark at gmail dot com
2011-07-31 10:26 ` [Bug c++/49921] " fabian.bergmark at gmail dot com
2011-07-31 10:38 ` [Bug c++/49921] [C++0x] " paolo.carlini at oracle dot com
2011-07-31 10:57 ` fabian.bergmark at gmail dot com [this message]
2011-08-01 9:52 ` redi at gcc dot gnu.org
2011-08-05 21:40 ` jason at gcc dot gnu.org
2011-08-06 4:37 ` jason at gcc dot gnu.org
2011-08-06 4:38 ` jason at gcc dot gnu.org
2011-08-06 22:23 ` 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-49921-4-pW5iPfw9zX@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).