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/89057] [8/9/10/11 Regression] AArch64 ld3 st4 less optimized Date: Mon, 04 Jan 2021 11:59:32 +0000 [thread overview] Message-ID: <bug-89057-4-Nx8Byum6eo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89057 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:b41e6dd50f329b0291457e939d4c0dacd81c82c1 commit r11-6439-gb41e6dd50f329b0291457e939d4c0dacd81c82c1 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Mon Jan 4 11:59:07 2021 +0000 aarch64: Improve vcombine codegen [PR89057] This patch fixes a codegen regression in the handling of things like: __temp.val[0] \ = vcombine_##funcsuffix (__b.val[0], \ vcreate_##funcsuffix (__AARCH64_UINT64_C (0))); \ in the 64-bit vst[234] functions. The zero was forced into a register at expand time, and we relied on combine to fuse the zero and combine back together into a single combinez pattern. The problem is that the zero could be hoisted before combine gets a chance to do its thing. gcc/ PR target/89057 * config/aarch64/aarch64-simd.md (aarch64_combine<mode>): Accept aarch64_simd_reg_or_zero for operand 2. Use the combinez patterns to handle zero operands. gcc/testsuite/ PR target/89057 * gcc.target/aarch64/pr89057.c: New test.
next prev parent reply other threads:[~2021-01-04 11:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89057-4@http.gcc.gnu.org/bugzilla/> 2020-03-24 15:13 ` [Bug target/89057] [8/9/10 " tnfchris at gcc dot gnu.org 2020-11-30 15:09 ` [Bug target/89057] [8/9/10/11 " abhiraj.garakapati at gmail dot com 2020-12-03 5:25 ` abhiraj.garakapati at gmail dot com 2020-12-30 10:24 ` rsandifo at gcc dot gnu.org 2021-01-04 11:59 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-04 12:07 ` [Bug target/89057] [8/9/10 " rsandifo at gcc dot gnu.org 2021-01-12 10:02 ` [Bug target/89057] [8/9 " rsandifo at gcc dot gnu.org 2021-05-14 9:51 ` [Bug target/89057] [9 " jakub at gcc dot gnu.org 2021-05-17 8:55 ` rsandifo 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-89057-4-Nx8Byum6eo@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).