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/105591] [13 Regression] ICE: in tree_to_poly_uint64, at tree.cc:3250 with -O -mavx512f -mno-avx2
Date: Fri, 13 May 2022 11:40:21 +0000 [thread overview]
Message-ID: <bug-105591-4-ssHl3Pd5yo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105591-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105591
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.0
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-05-13
Ever confirmed|0 |1
CC| |liuhongt at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. The offset is very large negative, built by simplify_bitfield_ref
here:
2416 tem = build3 (BIT_FIELD_REF, TREE_TYPE (op),
2417 p, op1, bitsize_int (idx * elem_size));
(gdb) p idx
$11 = 13704120150654661628
because we have a non-sensical permute:
x_4 = VEC_PERM_EXPR <u_3(D), u_3(D), { 13704120150654661630, 0 }>;
some sanity checking in simplify_bitfield_ref might be in order. Rejecting the
__builtin_shuffle might be another option, it's surely going to cause issues
elsewhere.
next prev parent reply other threads:[~2022-05-13 11:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:09 [Bug tree-optimization/105591] New: " zsojka at seznam dot cz
2022-05-13 11:40 ` rguenth at gcc dot gnu.org [this message]
2022-05-13 11:41 ` [Bug tree-optimization/105591] " crazylht at gmail dot com
2022-05-13 11:43 ` jakub at gcc dot gnu.org
2022-05-13 11:48 ` [Bug tree-optimization/105591] [13 Regression] ICE: in tree_to_poly_uint64, at tree.cc:3250 with -O -mavx512f -mno-avx2 since r13-379 zsojka at seznam dot cz
2022-05-13 11:50 ` jakub at gcc dot gnu.org
2022-05-13 11:54 ` crazylht at gmail dot com
2022-05-13 11:58 ` jakub at gcc dot gnu.org
2022-05-13 11:59 ` jakub at gcc dot gnu.org
2022-05-13 12:10 ` jakub at gcc dot gnu.org
2022-05-13 12:34 ` crazylht at gmail dot com
2022-05-13 12:43 ` jakub at gcc dot gnu.org
2022-05-13 12:45 ` crazylht at gmail dot com
2022-05-17 0:59 ` cvs-commit at gcc dot gnu.org
2022-05-17 1:01 ` crazylht at gmail dot com
2022-10-19 10:10 ` 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-105591-4-ssHl3Pd5yo@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).