public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97173] New: [11 Regression] ICE in vectorizable_live_operation, at tree-vect-loop.c:8324 since r11-3025-g095d42feed09f880 Date: Wed, 23 Sep 2020 07:41:47 +0000 [thread overview] Message-ID: <bug-97173-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97173 Bug ID: 97173 Summary: [11 Regression] ICE in vectorizable_live_operation, at tree-vect-loop.c:8324 since r11-3025-g095d42feed09f880 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- The following ICEs: $ cat disk.i typedef struct { char *track; char *clocks; char *fm; char *weak; } disk_t; disk_t disk_update_tlens_d; int disk_update_tlens_d_0; void disk_update_tlens() { disk_update_tlens_d.track = disk_update_tlens_d.clocks = disk_update_tlens_d.track + disk_update_tlens_d_0; disk_update_tlens_d.fm = disk_update_tlens_d.clocks + disk_update_tlens_d_0; disk_update_tlens_d.weak = disk_update_tlens_d.fm; disk_update_tlens_d.track[2] = 5; } $ gcc disk.i -c -O3 during GIMPLE pass: slp disk.i: In function ‘disk_update_tlens’: disk.i:11:6: internal compiler error: in vectorizable_live_operation, at tree-vect-loop.c:8348 11 | void disk_update_tlens() { | ^~~~~~~~~~~~~~~~~ 0x729e91 vectorizable_live_operation(vec_info*, _stmt_vec_info*, gimple_stmt_iterator*, _slp_tree*, _slp_instance*, int, bool, vec<stmt_info_for_cost, va_heap, vl_ptr>*) /home/marxin/Programming/gcc/gcc/tree-vect-loop.c:8348 0xfd1217 can_vectorize_live_stmts /home/marxin/Programming/gcc/gcc/tree-vect-stmts.c:10531 0xff6878 vect_transform_stmt(vec_info*, _stmt_vec_info*, gimple_stmt_iterator*, _slp_tree*, _slp_instance*) /home/marxin/Programming/gcc/gcc/tree-vect-stmts.c:10909 0x1022d69 vect_schedule_slp_instance /home/marxin/Programming/gcc/gcc/tree-vect-slp.c:4717 0x1022d86 vect_schedule_slp_instance /home/marxin/Programming/gcc/gcc/tree-vect-slp.c:4583 0x102bee1 vect_schedule_slp(vec_info*, vec<_slp_instance*, va_heap, vl_ptr>) /home/marxin/Programming/gcc/gcc/tree-vect-slp.c:4840 0x102d448 vect_slp_region /home/marxin/Programming/gcc/gcc/tree-vect-slp.c:3676 0x102d448 vect_slp_bb(basic_block_def*) /home/marxin/Programming/gcc/gcc/tree-vect-slp.c:3793 0x102fa6f execute /home/marxin/Programming/gcc/gcc/tree-vectorizer.c:1433 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-09-23 7:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-23 7:41 marxin at gcc dot gnu.org [this message] 2020-09-23 7:42 ` [Bug tree-optimization/97173] " marxin at gcc dot gnu.org 2020-09-23 8:06 ` rguenth at gcc dot gnu.org 2020-09-23 8:42 ` rguenth at gcc dot gnu.org 2020-09-23 10:19 ` cvs-commit at gcc dot gnu.org 2020-09-23 10:19 ` 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-97173-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).