public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ewlu at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114197] New: [14] middle-end: ICE in verify_dominators Date: Fri, 01 Mar 2024 21:44:15 +0000 [thread overview] Message-ID: <bug-114197-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114197 Bug ID: 114197 Summary: [14] middle-end: ICE in verify_dominators Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: ewlu at rivosinc dot com Target Milestone: --- Tested with riscv and x86_64 godbolt: https://godbolt.org/z/EvWj99d4b #pragma pack(push) struct a { volatile signed b : 8; }; #pragma pack(pop) int c; static struct a d = {5}; void e() { f: for (c = 8; c < 55; ++c) if (!d.b) goto f; } testcase.c: In function 'e': testcase.c:8:6: error: dominator of 7 should be 3, not 9 8 | void e() { | ^ during GIMPLE pass: vect dump file: testcase.c.179t.vect testcase.c:8:6: internal compiler error: in verify_dominators, at dominance.cc:1194 0xa0954c verify_dominators(cdi_direction) ../../../gcc/gcc/dominance.cc:1194 0x15e7ed1 checking_verify_dominators(cdi_direction) ../../../gcc/gcc/dominance.h:76 0x15e7ed1 slpeel_tree_duplicate_loop_to_edge_cfg(loop*, edge_def*, loop*, edge_def*, edge_def*, edge_def**, bool, vec<basic_block_def*, va_heap, vl_ptr>*) ../../../gcc/gcc/tree-vect-loop-manip.cc:1945 0x15ea20a vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) ../../../gcc/gcc/tree-vect-loop-manip.cc:3426 0x15d982e vect_transform_loop(_loop_vec_info*, gimple*) ../../../gcc/gcc/tree-vect-loop.cc:11935 0x161f981 vect_transform_loops ../../../gcc/gcc/tree-vectorizer.cc:1006 0x16200f3 try_vectorize_loop_1 ../../../gcc/gcc/tree-vectorizer.cc:1152 0x16200f3 try_vectorize_loop ../../../gcc/gcc/tree-vectorizer.cc:1182 0x162077c execute ../../../gcc/gcc/tree-vectorizer.cc:1298
next reply other threads:[~2024-03-01 21:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 21:44 ewlu at rivosinc dot com [this message] 2024-03-01 21:45 ` [Bug middle-end/114197] " ewlu at rivosinc dot com 2024-03-01 21:47 ` patrick at rivosinc dot com 2024-03-01 22:16 ` ewlu at rivosinc dot com 2024-03-04 9:23 ` [Bug middle-end/114197] [14 regression] " rguenth at gcc dot gnu.org 2024-03-04 10:47 ` rguenth at gcc dot gnu.org 2024-03-04 12:27 ` rguenth at gcc dot gnu.org 2024-03-04 13:19 ` rguenth at gcc dot gnu.org 2024-03-04 13:56 ` cvs-commit at gcc dot gnu.org 2024-03-04 13:56 ` 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-114197-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).