public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98849] [11 Regression] ICE in expand_shift_1, at expmed.c:2658 since g:7432f255b70811dafaf325d9403 Date: Wed, 27 Jan 2021 18:00:06 +0000 [thread overview] Message-ID: <bug-98849-4-i2YArl00LJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98849-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98849 --- Comment #11 from Christophe Lyon <clyon at gcc dot gnu.org> --- Yes MVE is incompatible with iWMMXt. Regarding the pattern name, quoting what I wrote in the commit message: I kept the mve_vshlq_<supf><mode> naming instead of renaming it to ashl3_<supf>_<mode> as discussed because the reference in arm_mve_builtins.def automatically inserts the "mve_" prefix and I didn't want to make a special case for this.
next prev parent reply other threads:[~2021-01-27 18:00 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 9:00 [Bug target/98849] New: " marxin at gcc dot gnu.org 2021-01-27 9:00 ` [Bug target/98849] " marxin at gcc dot gnu.org 2021-01-27 11:28 ` jakub at gcc dot gnu.org 2021-01-27 11:40 ` jakub at gcc dot gnu.org 2021-01-27 13:06 ` jakub at gcc dot gnu.org 2021-01-27 13:28 ` jakub at gcc dot gnu.org 2021-01-27 13:34 ` jakub at gcc dot gnu.org 2021-01-27 13:37 ` ktkachov at gcc dot gnu.org 2021-01-27 13:38 ` clyon at gcc dot gnu.org 2021-01-27 13:39 ` clyon at gcc dot gnu.org 2021-01-27 13:40 ` jakub at gcc dot gnu.org 2021-01-27 13:44 ` jakub at gcc dot gnu.org 2021-01-27 15:51 ` jakub at gcc dot gnu.org 2021-01-27 18:00 ` clyon at gcc dot gnu.org [this message] 2021-01-28 15:57 ` jakub at gcc dot gnu.org 2021-01-29 10:55 ` cvs-commit at gcc dot gnu.org 2021-01-29 11:03 ` jakub 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-98849-4-i2YArl00LJ@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).