public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111268] [14 Regression] internal compiler error: in to_constant, at poly-int.h:504 Date: Tue, 17 Oct 2023 12:44:13 +0000 [thread overview] Message-ID: <bug-111268-4-B8GGQzXNXp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111268-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 Last reconfirmed|2023-09-07 00:00:00 |2023-10-17 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Re-confirmed. during GIMPLE pass: slp t.c: In function 'f': t.c:3:6: internal compiler error: in to_constant, at poly-int.h:588 3 | void f(unsigned long *expected, svuint64_t values) { | ^ 0xe915f8 poly_int<2u, unsigned long>::to_constant() const /space/rguenther/src/gcc/gcc/poly-int.h:588 0x1aedf84 vectorizable_slp_permutation_1 /space/rguenther/src/gcc/gcc/tree-vect-slp.cc:8766 0x1aeee54 vectorizable_slp_permutation /space/rguenther/src/gcc/gcc/tree-vect-slp.cc:8931 0x1ae4321 vect_slp_analyze_node_operations_1 /space/rguenther/src/gcc/gcc/tree-vect-slp.cc:6049 the comment is outdated, we check unsigned olanes = ncopies * SLP_TREE_LANES (node); gcc_assert (repeating_p || multiple_p (olanes, nunits)); but then we have to adjust the following to poly arith somehow: if (repeating_p) vperm.quick_push ({{p.first, 0}, p.second + active_lane[p.first]}); else { /* We checked above that the vectors are constant-length. */ unsigned vnunits = TYPE_VECTOR_SUBPARTS (vtype).to_constant (); unsigned vi = (active_lane[p.first] + p.second) / vnunits; unsigned vl = (active_lane[p.first] + p.second) % vnunits; vperm.quick_push ({{p.first, vi}, vl});
next prev parent reply other threads:[~2023-10-17 12:44 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-01 12:56 [Bug target/111268] New: " malat at debian dot org 2023-09-01 12:57 ` [Bug target/111268] " malat at debian dot org 2023-09-01 12:57 ` malat at debian dot org 2023-09-01 12:59 ` malat at debian dot org 2023-09-02 3:22 ` [Bug tree-optimization/111268] [14 Regression] " pinskia at gcc dot gnu.org 2023-09-05 9:19 ` malat at debian dot org 2023-09-06 1:57 ` pinskia at gcc dot gnu.org 2023-09-06 2:15 ` pinskia at gcc dot gnu.org 2023-09-07 2:11 ` pinskia at gcc dot gnu.org 2023-10-17 12:44 ` rguenth at gcc dot gnu.org [this message] 2023-10-17 12:48 ` rguenth at gcc dot gnu.org 2024-01-04 8:16 ` pinskia at gcc dot gnu.org 2024-01-05 14:17 ` jakub at gcc dot gnu.org 2024-01-05 22:33 ` [Bug tree-optimization/111268] [11/12/13/14 " pinskia at gcc dot gnu.org 2024-01-16 11:41 ` jakub at gcc dot gnu.org 2024-01-18 18:33 ` pinskia at gcc dot gnu.org 2024-01-30 14:45 ` ricbal02 at gcc dot gnu.org 2024-02-01 17:08 ` ricbal02 at gcc dot gnu.org 2024-02-01 17:10 ` ricbal02 at gcc dot gnu.org 2024-02-01 17:20 ` cvs-commit at gcc dot gnu.org 2024-02-01 17:24 ` [Bug tree-optimization/111268] [11/12/13 " ricbal02 at gcc dot gnu.org 2024-05-08 12:46 ` cvs-commit at gcc dot gnu.org 2024-05-08 12:47 ` [Bug tree-optimization/111268] [11/12 " 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-111268-4-B8GGQzXNXp@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).