public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Tue, 23 Mar 2021 13:37:25 +0000 [thread overview]
Message-ID: <bug-99724-4-3jO2xqTNM8@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 #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
E.g. I can't find a neg pattern in iwmmxt.md either, so
r11-5990-g4cbb7cab47a3b91a12ad52baab5bbe6e4373ce73
is problematic too.
And r11-6616-g25bef68902f42f414f99626cefb2d3df81de7dc8 too (don't see any
UNSPEC_MISALIGNED_ACCESS in iwmmxt.md either.
and/ior/xor is, so that is likely ok.
So
--- gcc/config/arm/vec-common.md.jj 2021-03-23 10:21:07.096448805 +0100
+++ gcc/config/arm/vec-common.md 2021-03-23 14:36:54.823323029 +0100
@@ -202,13 +202,13 @@ (define_expand "xor<mode>3"
(define_expand "one_cmpl<mode>2"
[(set (match_operand:VDQ 0 "s_register_operand")
(not:VDQ (match_operand:VDQ 1 "s_register_operand")))]
- "ARM_HAVE_<MODE>_ARITH"
+ "ARM_HAVE_<MODE>_ARITH && !TARGET_REALLY_IWMMXT"
)
(define_expand "neg<mode>2"
[(set (match_operand:VDQWH 0 "s_register_operand" "")
(neg:VDQWH (match_operand:VDQWH 1 "s_register_operand" "")))]
- "ARM_HAVE_<MODE>_ARITH"
+ "ARM_HAVE_<MODE>_ARITH && !TARGER_REALLY_IWMMXT"
)
(define_expand "cadd<rot><mode>3"
@@ -281,7 +281,8 @@ (define_expand "movmisalign<mode>"
[(set (match_operand:VDQX 0 "neon_perm_struct_or_reg_operand")
(unspec:VDQX [(match_operand:VDQX 1 "neon_perm_struct_or_reg_operand")]
UNSPEC_MISALIGNED_ACCESS))]
- "ARM_HAVE_<MODE>_LDST && !BYTES_BIG_ENDIAN && unaligned_access"
+ "ARM_HAVE_<MODE>_LDST && !BYTES_BIG_ENDIAN
+ && unaligned_access && !TARGET_REALLY_IWMMXT"
{
rtx adjust_mem;
/* This pattern is not permitted to fail during expansion: if both arguments
instead?
next prev parent reply other threads:[~2021-03-23 13:37 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 [this message]
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
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-3jO2xqTNM8@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).