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/100887] [12 Regression] ICE: in ix86_expand_vector_init_concat, at config/i386/i386-expand.c:14178 with -mavx512f and __builtin_shufflevector() Date: Tue, 10 May 2022 08:18:19 +0000 [thread overview] Message-ID: <bug-100887-4-OZF4ud39PO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100887-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100887 --- Comment #14 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:2f5857a3ad1160a467c4c351820a450a7cff2d50 commit r10-10615-g2f5857a3ad1160a467c4c351820a450a7cff2d50 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Jun 4 11:20:02 2021 +0200 x86: Fix ix86_expand_vector_init for V*TImode [PR100887] We have vec_initv4tiv2ti and vec_initv2titi patterns which call ix86_expand_vector_init and assume it works for those modes. For the case of construction from two half-sized vectors, the code assumes it will always succeed, but we have only insn patterns with SImode and DImode element types. QImode and HImode element types are already handled by performing it with same sized vectors with SImode elements and the following patch extends that to V*TImode vectors. 2021-06-04 Jakub Jelinek <jakub@redhat.com> PR target/100887 * config/i386/i386-expand.c (ix86_expand_vector_init): Handle concatenation from half-sized modes with TImode elements. (cherry picked from commit b7dd2e4eeb44bc8678ecde8a6c7401de85e63561)
next prev parent reply other threads:[~2022-05-10 8:18 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 20:59 [Bug target/100887] New: " zsojka at seznam dot cz 2021-06-03 9:59 ` [Bug target/100887] " jakub at gcc dot gnu.org 2021-06-03 10:08 ` jakub at gcc dot gnu.org 2021-06-03 10:40 ` zsojka at seznam dot cz 2021-06-03 10:41 ` zsojka at seznam dot cz 2021-06-03 10:47 ` jakub at gcc dot gnu.org 2021-06-03 10:48 ` zsojka at seznam dot cz 2021-06-03 13:18 ` jakub at gcc dot gnu.org 2021-06-04 9:20 ` cvs-commit at gcc dot gnu.org 2021-06-07 7:29 ` cvs-commit at gcc dot gnu.org 2021-06-07 7:37 ` jakub at gcc dot gnu.org 2021-06-08 8:07 ` cvs-commit at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit 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-10 8:18 ` cvs-commit at gcc dot gnu.org 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-100887-4-OZF4ud39PO@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).