public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44561] using nullptr_t with -flto/-fwhopr causes ICE: tree code 'lang_type' is not supported in gimple streams Date: Mon, 11 Oct 2010 09:31:00 -0000 [thread overview] Message-ID: <20101011093100.-qB7Z89FAFFzjozeyWiWL3maMW5zDOcIo9PoGNJoj8E@z> (raw) In-Reply-To: <bug-44561-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44561 --- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-11 09:30:57 UTC --- New problems. typedef decltype(nullptr) nullptr_t; class shared_ptr { public: shared_ptr(nullptr_t __p); }; shared_ptr p = nullptr; exposes a nullptr constant (INTEGER_CST of LANG_TYPE). Of course build_int_cst_wide doesn't like this at all. From cp/decl.c:cxx_init_decl_processing(): nullptr_node = make_node (INTEGER_CST); TREE_TYPE (nullptr_node) = nullptr_type_node; :( One more reason to make NULLPTR_TYPE a regular middle-end tree code.
next prev parent reply other threads:[~2010-10-11 9:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44561-4@http.gcc.gnu.org/bugzilla/> 2010-09-27 16:39 ` rguenth at gcc dot gnu.org 2010-10-10 13:31 ` rguenth at gcc dot gnu.org 2010-10-10 13:53 ` rguenth at gcc dot gnu.org 2010-10-10 20:54 ` rguenth at gcc dot gnu.org 2010-10-11 9:31 ` rguenth at gcc dot gnu.org [this message] 2010-10-11 9:51 ` rguenth at gcc dot gnu.org 2010-10-14 12:00 ` rguenth at gcc dot gnu.org 2010-10-14 12:02 ` rguenth at gcc dot gnu.org 2010-06-16 20:17 [Bug c++/44561] New: " zsojka at seznam dot cz 2010-06-16 20:40 ` [Bug c++/44561] " rguenth 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=20101011093100.-qB7Z89FAFFzjozeyWiWL3maMW5zDOcIo9PoGNJoj8E@z \ --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: linkBe 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).