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/99813] [11 Regression] SVE: Invalid assembly at -O3 (multiplier out of range in incb instruction) Date: Wed, 31 Mar 2021 13:29:03 +0000 [thread overview] Message-ID: <bug-99813-4-50X1tH37Xs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99813-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99813 --- Comment #9 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:3753ceff562d8614a94a164b312f389812bd6cd8 commit r10-9641-g3753ceff562d8614a94a164b312f389812bd6cd8 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Mar 31 10:46:01 2021 +0200 aarch64: Fix up *add<mode>3_poly_1 [PR99813] As mentioned in the PR, Uai constraint stands for aarch64_sve_scalar_inc_dec_immediate while Uav for aarch64_sve_addvl_addpl_immediate. Both *add<mode>3_aarch64 and *add<mode>3_poly_1 patterns use * return aarch64_output_sve_scalar_inc_dec (operands[2]); * return aarch64_output_sve_addvl_addpl (operands[2]); in that order, but the former with Uai,Uav order, while the latter with Uav,Uai instead. This patch swaps the constraints so that they match the output. Co-authored-by: Richard Sandiford <richard.sandiford@arm.com> 2021-03-31 Jakub Jelinek <jakub@redhat.com> Richard Sandiford <richard.sandiford@arm.com> PR target/99813 * config/aarch64/aarch64.md (*add<mode>3_poly_1): Swap Uai and Uav constraints on operands[2] and similarly 0 and rk constraints on operands[1] corresponding to that. * g++.target/aarch64/sve/pr99813.C: New test. (cherry picked from commit c001c194a2f73fb32461b597e91a35f9bbcf4414)
prev parent reply other threads:[~2021-03-31 13:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 9:16 [Bug target/99813] New: " acoplan at gcc dot gnu.org 2021-03-29 9:22 ` [Bug target/99813] [11 Regression] " ktkachov at gcc dot gnu.org 2021-03-30 9:18 ` jakub at gcc dot gnu.org 2021-03-30 9:46 ` jakub at gcc dot gnu.org 2021-03-30 15:20 ` rsandifo at gcc dot gnu.org 2021-03-30 15:58 ` jakub at gcc dot gnu.org 2021-03-30 16:10 ` jakub at gcc dot gnu.org 2021-03-31 8:48 ` cvs-commit at gcc dot gnu.org 2021-03-31 8:49 ` jakub at gcc dot gnu.org 2021-03-31 13:29 ` cvs-commit at gcc dot gnu.org [this message]
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-99813-4-50X1tH37Xs@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).