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/99808] [8/9/10/11 Regression] ICE in as_a, at machmode.h:365 Date: Wed, 31 Mar 2021 09:39:00 +0000 [thread overview] Message-ID: <bug-99808-4-30slYc4aad@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99808-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99808 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>: https://gcc.gnu.org/g:1a92899b08e61d503a2897f2f66b064eb84706bc commit r10-9628-g1a92899b08e61d503a2897f2f66b064eb84706bc Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com> Date: Mon Mar 29 11:52:24 2021 +0100 aarch64: PR target/99037 Fix RTL represntation in move_lo_quad patterns This patch fixes the RTL representation of the move_lo_quad patterns to use aarch64_simd_or_scalar_imm_zero for the zero part rather than a vec_duplicate of zero or a const_int 0. The expander that generates them is also adjusted so that we use and match the correct const_vector forms throughout. Co-Authored-By: Jakub Jelinek <jakub@redhat.com> gcc/ChangeLog: PR target/99037 * config/aarch64/aarch64-simd.md (move_lo_quad_internal_<mode>): Use aarch64_simd_or_scalar_imm_zero to match zeroes. Remove pattern matching const_int 0. (move_lo_quad_internal_be_<mode>): Likewise. (move_lo_quad_<mode>): Update for the above. * config/aarch64/iterators.md (VQ_2E): Delete. gcc/testsuite/ChangeLog: PR target/99808 * gcc.target/aarch64/pr99808.c: New test.
next prev parent reply other threads:[~2021-03-31 9:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 6:58 [Bug debug/99808] New: " asolokha at gmx dot com 2021-03-29 7:48 ` [Bug target/99808] " rguenth at gcc dot gnu.org 2021-03-29 9:02 ` jakub at gcc dot gnu.org 2021-03-29 9:03 ` jakub at gcc dot gnu.org 2021-03-29 9:14 ` jakub at gcc dot gnu.org 2021-03-29 10:16 ` jakub at gcc dot gnu.org 2021-03-29 10:21 ` ktkachov at gcc dot gnu.org 2021-03-29 10:55 ` cvs-commit at gcc dot gnu.org 2021-03-30 13:08 ` cvs-commit at gcc dot gnu.org 2021-03-31 9:39 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-31 9:39 ` cvs-commit at gcc dot gnu.org 2021-05-07 10:36 ` cvs-commit at gcc dot gnu.org 2021-05-07 10:38 ` cvs-commit at gcc dot gnu.org 2021-05-07 14:14 ` cvs-commit at gcc dot gnu.org 2021-05-07 14:16 ` 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-99808-4-30slYc4aad@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).