public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/95320] New: [11 Regression] ICE in odr_type_p, at ipa-utils.h:246, during IPA pass: pure-const Date: Mon, 25 May 2020 16:47:28 +0000 [thread overview] Message-ID: <bug-95320-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95320 Bug ID: 95320 Summary: [11 Regression] ICE in odr_type_p, at ipa-utils.h:246, during IPA pass: pure-const Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: ams at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- For some reason, this only occurs when compiling for AMDGCN and it seems to be a recent regression. The issue seems to affect nearly all testcases in libgomp, I get 2500+ FAIL. For instance gcc -fopenmp libgomp/testsuite/libgomp.c-c++-common/for-11.c fails as: during IPA pass: fnsummary src/gcc-mainline/libgomp/testsuite/libgomp.c-c++-common/for-11.c:5: internal compiler error: in odr_type_p, at ipa-utils.h:246 0x8b3ccf odr_type_p(tree_node const*) gcc-mainline/gcc/ipa-utils.h:246 0x8b3ccf local_tree_p gcc-mainline/gcc/lto-streamer-out.c:594 0x8b3ccf DFS::DFS(output_block*, tree_node*, bool, bool, bool) gcc-mainline/gcc/lto-streamer-out.c:639 Breakpoint 1, DFS::DFS(output_block*, tree_node*, bool, bool, bool) () at gcc-mainline/gcc/lto-streamer-out.c:639 639 if (ob->local_trees && local_tree_p (expr)) (gdb) p ob $1 = <optimized out> (gdb) p expr $2 = (tree) 0x7ffff734ac78 (gdb) p debug_tree(expr) <record_type 0x7ffff734ac78 .omp_data_t.89 TI
next reply other threads:[~2020-05-25 16:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-25 16:47 burnus at gcc dot gnu.org [this message] 2020-05-25 16:59 ` [Bug ipa/95320] " burnus at gcc dot gnu.org 2020-05-26 7:19 ` rguenth at gcc dot gnu.org 2020-05-26 7:37 ` burnus at gcc dot gnu.org 2020-05-26 14:51 ` burnus at gcc dot gnu.org 2020-05-26 16:26 ` cvs-commit at gcc dot gnu.org 2020-05-26 16:28 ` burnus at gcc dot gnu.org 2020-08-21 15:15 ` cvs-commit 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-95320-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).