public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107303] [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() since r13-2978-g43faf3e5445b5717 Date: Tue, 18 Oct 2022 12:46:19 +0000 [thread overview] Message-ID: <bug-107303-4-qvBwOmdj7H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107303 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- One can see it in the original dump: (void) (u0 = TARGET_EXPR <D.2387, BIT_FIELD_REF < VEC_PERM_EXPR < TARGET_EXPR <D.2386, BIT_FIELD_REF < VEC_PERM_EXPR < {u1, { 0 }, { 0 }, { 0 }} , v , { 6, 4, 2, 3 } > , 32, 0>> , {u2, { 0 }} , { 0, 1 } > , 16, 0>>;, u0 * D.2388;) where it used to be: (void) (u0 = TARGET_EXPR <D.2388, TARGET_EXPR <D.2387, BIT_FIELD_REF < VEC_PERM_EXPR < TARGET_EXPR <D.2386, BIT_FIELD_REF < VEC_PERM_EXPR < {u1, { 0 }, { 0 }, { 0 }} , v , { 6, 4, 2, 3 } > , 32, 0>> , {u2, { 0 }} , { 0, 1 } > , 16, 0>>>;, u0 * D.2388;) before but the removal of D.2388 TARGET_EXPR left D.2388 use in the IL without it being initialized anywhere.
next prev parent reply other threads:[~2022-10-18 12:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 11:26 [Bug c++/107303] New: [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() zsojka at seznam dot cz 2022-10-18 11:40 ` [Bug c++/107303] [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() since r13-2978-g43faf3e5445b5717 marxin at gcc dot gnu.org 2022-10-18 12:44 ` jakub at gcc dot gnu.org 2022-10-18 12:46 ` jakub at gcc dot gnu.org [this message] 2022-10-18 12:46 ` jakub at gcc dot gnu.org 2023-01-23 21:16 ` jason at gcc dot gnu.org 2023-01-24 3:26 ` cvs-commit at gcc dot gnu.org 2023-01-24 3:26 ` jason 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-107303-4-qvBwOmdj7H@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).