public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/97133] New: [11 Regression] ICE: tree code 'bind_expr' is not supported in LTO streams Date: Mon, 21 Sep 2020 04:59:01 +0000 [thread overview] Message-ID: <bug-97133-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97133 Bug ID: 97133 Summary: [11 Regression] ICE: tree code 'bind_expr' is not supported in LTO streams Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com CC: marxin at gcc dot gnu.org Target Milestone: --- gcc-11.0.0-alpha20200920 snapshot (g:363e7755f227656684c8e284307ceee451503ca4) ICEs when compiling gcc/testsuite/gcc.dg/pr88701.c w/ -flto: % gcc-11.0.0 -flto -c gcc/testsuite/gcc.dg/pr88701.c during IPA pass: modref gcc/testsuite/gcc.dg/pr88701.c:18:1: internal compiler error: tree code 'bind_expr' is not supported in LTO streams 18 | } | ^ 0xc3d22c lto_write_tree /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:554 0xc3d22c lto_output_tree_1 /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:592 0xc45b49 DFS::DFS(output_block*, tree_node*, bool, bool, bool) /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:892 0xc46b30 lto_output_tree(output_block*, tree_node*, bool, bool) /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:1853 0xc47d7d streamer_write_chain /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:2370 0xc47d7d output_function /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:2408 0xc47d7d lto_output() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/lto-streamer-out.c:2792 0xcc6611 write_lto /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/passes.c:2621 0xcc6611 ipa_write_summaries_1 /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/passes.c:2685 0xcc6611 ipa_write_summaries() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/passes.c:2740 0x96616d ipa_passes /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/cgraphunit.c:2689 0x96616d symbol_table::compile() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/cgraphunit.c:2776 0x968222 symbol_table::compile() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/cgraphunit.c:2756 0x968222 symbol_table::finalize_compilation_unit() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200920/work/gcc-11-20200920/gcc/cgraphunit.c:3021
next reply other threads:[~2020-09-21 4:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 4:59 asolokha at gmx dot com [this message] 2020-09-21 7:01 ` [Bug ipa/97133] " rguenth at gcc dot gnu.org 2020-09-24 5:26 ` asolokha at gmx dot com 2020-10-01 14:01 ` hubicka at gcc dot gnu.org 2020-10-01 15:36 ` [Bug lto/97133] " msebor 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-97133-4@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: 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).