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:48:37 +0000	[thread overview]
Message-ID: <bug-111268-4-ZkiyVTvvn7@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

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, we have

(gdb) p debug (node)
t.c:3:6: note: node 0x3f341d0 (max_nunits=1, refcnt=1) vector(2) long unsigned
int
t.c:3:6: note: op: VEC_PERM_EXPR
t.c:3:6: note:  stmt 0 _1 = BIT_FIELD_REF <values_7(D), 64, 0>;
t.c:3:6: note:  stmt 1 _4 = BIT_FIELD_REF <values_7(D), 64, 64>;
t.c:3:6: note:  lane permutation { 0[0] 0[1] }
t.c:3:6: note:  children 0x3f34260
$1 = void
(gdb) p vtype
$2 = <vector_type 0x7ffff6ca6bd0 svuint64_t>

it looks like "compatibility" somehow requires/allows us to V_C_E the
permuted argument to a fixed length vector?  Otherwise vect_build_slp_tree_1
of course could check the BIT_FIELD_REF args are fixed length.

  parent reply	other threads:[~2023-10-17 12:48 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
2023-10-17 12:48 ` rguenth at gcc dot gnu.org [this message]
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-ZkiyVTvvn7@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: link
Be 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).