public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101046] ICE: in gen_rtx_CONST_VECTOR, at emit-rtl.c:6031 with -mavx512vbmi -mavx512vl Date: Tue, 10 May 2022 08:18:40 +0000 [thread overview] Message-ID: <bug-101046-4-um04fTfpTq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101046-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101046 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:8f79b09894c6037d0a376be239567ebdce42ea0e commit r10-10619-g8f79b09894c6037d0a376be239567ebdce42ea0e Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jun 15 11:36:47 2021 +0200 expr: Fix up VEC_PACK_TRUNC_EXPR expansion [PR101046] The following testcase ICEs, because we have a mode mismatch. VEC_PACK_TRUNC_EXPR's operands have different modes from the result (same vector mode size but twice as large element), but we were passing non-NULL subtarget with the mode of the result to the expansion of its arguments, so the VEC_PERM_EXPR in one of the operands which had V8SImode operands and result had V16HImode target. Fixed by clearing the subtarget if we are changing mode. 2021-06-15 Jakub Jelinek <jakub@redhat.com> PR target/101046 * expr.c (expand_expr_real_2) <case VEC_PACK_FIX_TRUNC_EXPR, case VEC_PACK_TRUNC_EXPR>: Clear subtarget when changing mode. (cherry picked from commit 008153c8435ca3bf587e11654c31f05c0f99b43a)
next prev parent reply other threads:[~2022-05-10 8:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-13 10:37 [Bug target/101046] New: " zsojka at seznam dot cz 2021-06-13 19:16 ` [Bug target/101046] " jakub at gcc dot gnu.org 2021-06-14 9:07 ` marxin at gcc dot gnu.org 2021-06-14 9:16 ` jakub at gcc dot gnu.org 2021-06-15 9:37 ` cvs-commit at gcc dot gnu.org 2021-06-15 9:58 ` jakub at gcc dot gnu.org 2021-06-15 9:59 ` jakub at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-11 6:20 ` cvs-commit 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-101046-4-um04fTfpTq@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).