public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/106783] New: [12/13 Regression] ICE in ipa-modref.cc:analyze_function Date: Wed, 31 Aug 2022 08:58:26 +0000 [thread overview] Message-ID: <bug-106783-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106783 Bug ID: 106783 Summary: [12/13 Regression] ICE in ipa-modref.cc:analyze_function Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: amonakov at gcc dot gnu.org CC: amonakov at gcc dot gnu.org, asolokha at gmx dot com, marxin at gcc dot gnu.org, unassigned at gcc dot gnu.org Target Milestone: --- +++ This bug was initially created as a clone of Bug #106781 +++ ICEs when emitting a tree dump with -O2 -fdump-tree-modref2 int n; __attribute__ ((noinline,noclone,returns_twice)) static int bar (int) { n /= 0; return n; } int foo (int x) { return bar (x); } t.c: In function ‘foo’: t.c:12:1: internal compiler error: in analyze_function, at ipa-modref.cc:3286 12 | foo (int x) | ^~~ 0x10e548e analyze_function gcc/ipa-modref.cc:3286 0x10e83b5 execute gcc/ipa-modref.cc:4186 Note that -fdump-tree-modref2 is needed. It reaches a gcc_unreachable(), I'd suggest to move the verification outside of dumping if possible, so the compiler doesn't ICE or not depending on whether dumping is requested.
next reply other threads:[~2022-08-31 8:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-31 8:58 amonakov at gcc dot gnu.org [this message] 2022-08-31 9:06 ` [Bug ipa/106783] [12/13 Regression] ICE in ipa-modref.cc:analyze_function since r12-5247-ga34edf9a3e907de2 marxin at gcc dot gnu.org 2022-08-31 12:15 ` rguenth at gcc dot gnu.org 2022-10-19 6:53 ` rguenth at gcc dot gnu.org 2023-05-08 12:25 ` [Bug ipa/106783] [12/13/14 " rguenth at gcc dot gnu.org 2024-02-12 17:31 ` pinskia 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-106783-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).