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/99727] [11 Regression] MVE: ICE (segfault) in arm_print_operand at -O3 since r11-6616-g25bef689 Date: Wed, 24 Mar 2021 14:23:06 +0000 [thread overview] Message-ID: <bug-99727-4-NURseOzZAF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99727-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99727 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>: https://gcc.gnu.org/g:79cdbabbc4cbf79491c274220928406dff3d4039 commit r11-7816-g79cdbabbc4cbf79491c274220928406dff3d4039 Author: Christophe Lyon <christophe.lyon@linaro.org> Date: Wed Mar 24 08:51:41 2021 +0000 arm: Fix MVE constraints for movmisalign [PR target/99727] MVE has different constraints than Neon for load/store: we should use the Ux constraint instead of Um. 2021-03-24 Christophe Lyon <christophe.lyon@linaro.org> PR target/99727 gcc/ * config/arm/mve.md (movmisalign<mode>_mve_store): Use Ux constraint. (movmisalign<mode>_mve_load): Likewise. gcc/testsuite/ * gcc.target/arm/pr99727.c: New test.
next prev parent reply other threads:[~2021-03-24 14:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 12:45 [Bug target/99727] New: [11 Regression] MVE: ICE (segfault) in arm_print_operand at -O3 acoplan at gcc dot gnu.org 2021-03-23 12:45 ` [Bug target/99727] " acoplan at gcc dot gnu.org 2021-03-23 14:16 ` [Bug target/99727] [11 Regression] MVE: ICE (segfault) in arm_print_operand at -O3 since r11-6616-g25bef689 acoplan at gcc dot gnu.org 2021-03-23 21:55 ` clyon at gcc dot gnu.org 2021-03-24 8:32 ` rguenth at gcc dot gnu.org 2021-03-24 14:23 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-24 14:24 ` clyon at gcc dot gnu.org 2021-03-24 14:28 ` acoplan 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-99727-4-NURseOzZAF@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).