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:27:30 +0000 [thread overview] Message-ID: <bug-113163-4-PlvJlH068W@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 #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- While higher at the call stack: #3 0x000000000148714f in vect_transform_loop (loop_vinfo=loop_vinfo@entry=0x350f2a0, loop_vectorized_call=loop_vectorized_call@entry=0x0) at src/gcc-mainline/gcc/tree-vect-loop.cc:11911 11911 epilogue = vect_do_peeling (loop_vinfo, niters, nitersm1, &niters_vector, (gdb) p debug_tree(niters) <integer_cst 0x7ffff7bb2030 type <integer_type 0x7ffff7b5e3f0> constant 6> One level down: #2 0x0000000001498154 in vect_do_peeling (loop_vinfo=loop_vinfo@entry=0x350f2a0, niters=<optimized out>, niters@entry=0x7ffff7bb2030, nitersm1=nitersm1@entry=0x7ffff7bb2c78, niters_vector=niters_vector@entry=0x7fffffffda60, step_vector=step_vector@entry=0x7fffffffda68, niters_vector_mult_vf_var=niters_vector_mult_vf_var@entry=0x7fffffffda70, th=<optimized out>, check_profitability=<optimized out>, niters_no_overflow=<optimized out>, advance=<optimized out>) at src/gcc-mainline/gcc/tree-vect-loop-manip.cc:3399 3399 vect_update_ivs_after_vectorizer (loop_vinfo, niters_vector_mult_vf, where niters_vector_mult_vf is ssa_name that fails in the assert. The variable seems to be generated a few lines up in the same function (line 3375 and following): if (!integer_onep (*step_vector)) { /* On exit from the loop we will have an easy way of calcalating NITERS_VECTOR / STEP * STEP. Install a dummy definition until then. */ niters_vector_mult_vf = make_ssa_name (TREE_TYPE (*niters_vector)); SSA_NAME_DEF_STMT (niters_vector_mult_vf) = gimple_build_nop (); *niters_vector_mult_vf_var = niters_vector_mult_vf; } else vect_gen_vector_loop_niters_mult_vf (loop_vinfo, *niters_vector, &niters_vector_mult_vf);
next prev parent reply other threads:[~2023-12-28 12:27 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 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 [this message] 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-PlvJlH068W@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).