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 middle-end/113163] [14 Regression][GCN] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 Date: Thu, 28 Dec 2023 12:20:00 +0000 [thread overview] Message-ID: <bug-113163-4-OVQSVFWaUl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113163-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113163 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 56958 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56958&action=edit Reduced testcase ( $ amdgcn-amdhsa-gcc -g -O2 inp5.i -march=gfx900 during GIMPLE pass: vect inp5.i: In function '_l64a_r': inp5.i:4:1: internal compiler error: in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 4 | _l64a_r (struct _reent *rptr, | ^~~~~~~ 0x94cc17 vect_peel_nonlinear_iv_init(gimple**, tree_node*, tree_node*, tree_node*, vect_induction_op_type) /net/build5-fossa-cs/scratch/tburnus/fsf.mainline.x86_64-linux-gnu-amdgcn/src/gcc-mainline/gcc/tree-vect-loop.cc:9420 0x148bb04 vect_update_ivs_after_vectorizer src/gcc-mainline/gcc/tree-vect-loop-manip.cc:2267 0x1498153 vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) src/gcc-mainline/gcc/tree-vect-loop-manip.cc:3399 0x148714e vect_transform_loop(_loop_vec_info*, gimple*) src/gcc-mainline/gcc/tree-vect-loop.cc:11911 0x14c9544 vect_transform_loops src/gcc-mainline/gcc/tree-vectorizer.cc:1006 0x14c9bc3 try_vectorize_loop_1 src/gcc-mainline/gcc/tree-vectorizer.cc:1152 0x14c9bc3 try_vectorize_loop src/gcc-mainline/gcc/tree-vectorizer.cc:1182 0x14ca224 execute src/gcc-mainline/gcc/tree-vectorizer.cc:1298 * * * Breakpoint 1, vect_peel_nonlinear_iv_init (stmts=0x7fffffffd698, init_expr=0x7ffff7a56948, skip_niters=0x7ffff7bb8798, step_expr=0x7ffff7a64ba0, induction_type=vect_step_op_shr) at src/gcc-mainline/gcc/tree-vect-loop.cc:9420 9420 gcc_assert (TREE_CODE (skip_niters) == INTEGER_CST); (gdb) p debug_tree(skip_niters) <ssa_name 0x7ffff7bb8798 type <integer_type 0x7ffff7b5e3f0 public unsigned SI size <integer_cst 0x7ffff7a64768 constant 32> unit-size <integer_cst 0x7ffff7a64780 constant 4> align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 0x7ffff7b5e3f0 precision:32 min <integer_cst 0x7ffff7b752d0 0> max <integer_cst 0x7ffff7a64b28 4294967295>> def_stmt GIMPLE_NOP version:54> $2 = void
next prev parent reply other threads:[~2023-12-28 12:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-28 11:37 [Bug middle-end/113163] New: " burnus at gcc dot gnu.org 2023-12-28 11:53 ` [Bug middle-end/113163] " tnfchris at gcc dot gnu.org 2023-12-28 12:20 ` burnus at gcc dot gnu.org [this message] 2023-12-28 12:22 ` tnfchris at gcc dot gnu.org 2023-12-28 12:25 ` tnfchris at gcc dot gnu.org 2023-12-28 12:27 ` burnus at gcc dot gnu.org 2023-12-28 12:30 ` burnus at gcc dot gnu.org 2023-12-28 14:20 ` tnfchris at gcc dot gnu.org 2023-12-28 14:20 ` tnfchris at gcc dot gnu.org 2023-12-29 14:48 ` tnfchris at gcc dot gnu.org 2023-12-29 21:06 ` tnfchris at gcc dot gnu.org 2024-01-02 11:29 ` ams at gcc dot gnu.org 2024-01-02 11:35 ` tnfchris at gcc dot gnu.org 2024-01-06 6:14 ` pinskia at gcc dot gnu.org 2024-01-09 11:18 ` cvs-commit at gcc dot gnu.org 2024-01-09 11:25 ` tnfchris 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-113163-4-OVQSVFWaUl@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).