public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/108511] New: [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 Date: Tue, 24 Jan 2023 08:36:04 +0000 [thread overview] Message-ID: <bug-108511-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108511 Bug ID: 108511 Summary: [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- Host: *-*-solaris2.11 Target: *-*-solaris2.11 Build: *-*-solaris2.11 Between 20230120 (99ea0d7611605d2d1a67a6021cb78f0bdd5c609b) and 20230123 (b457cab64038cd9b7a8481594ff673f1822681f6), a lto test regressed on Solaris (both sparc and x86, 32 and 64-bit): +FAIL: g++.dg/lto/pr88049 cp_lto_pr88049_0.o-cp_lto_pr88049_0.o link, -flto -O2 -w (internal compiler error: in possibly_call_in_translation_unit_p, at cgraph.cc:4184) during IPA pass: fnsummary lto1: internal compiler error: in possibly_call_in_translation_unit_p, at cgraph.cc:4184 0x8c9a54d cgraph_edge::possibly_call_in_translation_unit_p() /vol/gcc/src/hg/master/local/gcc/cgraph.cc:4184 0x8f6c80d ipa_read_edge_info /vol/gcc/src/hg/master/local/gcc/ipa-prop.cc:5083 0x8f6cdc7 ipa_read_node_info /vol/gcc/src/hg/master/local/gcc/ipa-prop.cc:5168 0x8f6cdc7 ipa_prop_read_section /vol/gcc/src/hg/master/local/gcc/ipa-prop.cc:5251 0x8f6cdc7 ipa_prop_read_jump_functions() /vol/gcc/src/hg/master/local/gcc/ipa-prop.cc:5278 0x8f230c2 ipa_fn_summary_read /vol/gcc/src/hg/master/local/gcc/ipa-fnsummary.cc:4638 0x90cb1cc ipa_read_summaries_1 /vol/gcc/src/hg/master/local/gcc/passes.cc:3001 0x8bf1eb4 read_cgraph_and_symbols(unsigned int, char const**) /vol/gcc/src/hg/master/local/gcc/lto/lto-common.cc:2936 0x8bd5825 lto_main() /vol/gcc/src/hg/master/local/gcc/lto/lto.cc:654
next reply other threads:[~2023-01-24 8:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-24 8:36 ro at gcc dot gnu.org [this message] 2023-01-24 8:36 ` [Bug ipa/108511] " ro at gcc dot gnu.org 2023-01-25 9:19 ` [Bug ipa/108511] [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 since r13-5285-g106f99406312d7ed marxin at gcc dot gnu.org 2023-01-25 9:20 ` marxin at gcc dot gnu.org 2023-01-25 10:02 ` rguenth at gcc dot gnu.org 2023-01-25 10:30 ` marxin at gcc dot gnu.org 2023-01-25 12:07 ` rguenth at gcc dot gnu.org 2023-01-25 12:08 ` rguenth at gcc dot gnu.org 2023-01-29 0:01 ` hubicka at gcc dot gnu.org 2023-01-30 8:35 ` cvs-commit at gcc dot gnu.org 2023-01-30 8:35 ` rguenth 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-108511-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).