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: Thu, 14 Oct 2010 12:00:00 -0000 [thread overview]
Message-ID: <20101014120000.MAWR6J6e0OLk5LjBE5rrkXmHvc7bt0-KckWadCHDEaE@z> (raw)
In-Reply-To: <bug-44561-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44561
--- Comment #8 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-14 11:59:50 UTC ---
Author: rguenth
Date: Thu Oct 14 11:59:47 2010
New Revision: 165462
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=165462
Log:
2010-10-14 Richard Guenther <rguenther@suse.de>
PR lto/44561
* tree.def (NULLPTR_TYPE): New tree code.
* dbxout.c (dbxout_type): Handle NULLPTR_TYPE.
* dwarf2out.c (is_base_type): Likewise.
(gen_type_die_with_usage): Likewise.
* sdbout.c (plain_type_1): Likewise.
* tree.c (build_int_cst_wide): Likewise.
* gimple.c (gimple_types_compatible_p_1): NULLPTR_TYPE types
are equal.
cp/
* cp-tree.h (NULLPTR_TYPE_P): Adjust.
* decl.c (cxx_init_decl_processing): Build a NULLPTR_TYPE node,
use build_int_cst.
* error.c (dump_type): Handle NULLPTR_TYPE.
(dump_type_prefix): Likewise.
(dump_type_suffix): Likewise.
* mangle.c (write_type): Likewise.
* name-lookup.c (arg_assoc_type): Likewise.
* rtti.c (typeinfo_in_lib_p): Likewise.
* pt.c (tsubst): Likewise.
* g++.dg/lto/20101010-3_0.C: New testcase.
* g++.dg/lto/20101010-4_0.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/lto/20101010-3_0.C
trunk/gcc/testsuite/g++.dg/lto/20101010-4_0.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/decl.c
trunk/gcc/cp/error.c
trunk/gcc/cp/mangle.c
trunk/gcc/cp/name-lookup.c
trunk/gcc/cp/pt.c
trunk/gcc/cp/rtti.c
trunk/gcc/dbxout.c
trunk/gcc/dwarf2out.c
trunk/gcc/gimple.c
trunk/gcc/sdbout.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree.c
trunk/gcc/tree.def
next prev parent reply other threads:[~2010-10-14 12:00 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
2010-10-11 9:51 ` rguenth at gcc dot gnu.org
2010-10-14 12:00 ` rguenth at gcc dot gnu.org [this message]
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=20101014120000.MAWR6J6e0OLk5LjBE5rrkXmHvc7bt0-KckWadCHDEaE@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: 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).