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/99724] [11 Regression] CE in in extract_insn, at recog.c:2770
Date: Wed, 24 Mar 2021 10:23:40 +0000 [thread overview]
Message-ID: <bug-99724-4-dobsltJN9e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99724-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99724
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:4f992de4f369e17b64a66246ec35bf75f41dc98d
commit r11-7814-g4f992de4f369e17b64a66246ec35bf75f41dc98d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 24 11:22:35 2021 +0100
arm: Fix some more vec-common.md patterns for iwmmxt [PR99724]
The following patch fixes similar issues as in PR98849;
in older gcc versions, the expanders were present in neon.md guarded
with TARGET_NEON, but they got moved to vec-common.md and guarded with
ARM_HAVE_<MODE>_ARITH so that they handle both MVE and Neon.
The macros are enabled for some modes even for iwmmxt which has some
vector support for those modes, but only limited. In particular,
neither the one_cmpl, nor neg, nor movmisalign patterns are present.
For some reason I've failed to construct something that ICEs with
movmisalign, so that is not covered by the testsuite, but both
one_cmpl and neg ICE.
2021-03-24 Jakub Jelinek <jakub@redhat.com>
PR target/99724
* config/arm/vec-common.md (one_cmpl<mode>2, neg<mode>2,
movmisalign<mode>): Disable expanders for TARGET_REALLY_IWMMXT.
* gcc.target/arm/pr99724.c: New test.
next prev parent reply other threads:[~2021-03-24 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 10:25 [Bug target/99724] New: " marxin at gcc dot gnu.org
2021-03-23 10:35 ` [Bug target/99724] " rguenth at gcc dot gnu.org
2021-03-23 13:09 ` rearnsha at gcc dot gnu.org
2021-03-23 13:22 ` jakub at gcc dot gnu.org
2021-03-23 13:37 ` jakub at gcc dot gnu.org
2021-03-23 13:57 ` clyon at gcc dot gnu.org
2021-03-23 19:49 ` jakub at gcc dot gnu.org
2021-03-23 21:19 ` clyon at gcc dot gnu.org
2021-03-24 10:23 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-24 10:24 ` 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-99724-4-dobsltJN9e@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: link
Be 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).