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/99437] [11 Regression] Error: immediate value out of range 1 to 8 at operand 3 -- `shrn v1.8b,v1.8h,15'
Date: Mon, 08 Mar 2021 15:06:21 +0000 [thread overview]
Message-ID: <bug-99437-4-RfubB3GGPD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99437-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>:
https://gcc.gnu.org/g:0d9a70ea3881c284b7689b691d54d047b55b486d
commit r11-7556-g0d9a70ea3881c284b7689b691d54d047b55b486d
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date: Mon Mar 8 15:05:21 2021 +0000
aarch64: Fix PR99437 - tighten shift predicates for narrowing shift
patterns
In this bug combine forms the (R)SHRN(2) instructions with an invalid shift
amount.
The intrinsic expanders for these patterns validate the right shift amount
but if the
final patterns end up being matched by combine (or other RTL passes I
suppose) they
still let the wrong const_vector through.
This patch tightens up the predicates for the instructions involved by
using predicates
for the right shift amount const_vectors.
gcc/ChangeLog:
PR target/99437
* config/aarch64/predicates.md (aarch64_simd_shift_imm_vec_qi):
Define.
(aarch64_simd_shift_imm_vec_hi): Likewise.
(aarch64_simd_shift_imm_vec_si): Likewise.
(aarch64_simd_shift_imm_vec_di): Likewise.
* config/aarch64/aarch64-simd.md (aarch64_shrn<mode>_insn_le): Use
predicate from above.
(aarch64_shrn<mode>_insn_be): Likewise.
(aarch64_rshrn<mode>_insn_le): Likewise.
(aarch64_rshrn<mode>_insn_be): Likewise.
(aarch64_shrn2<mode>_insn_le): Likewise.
(aarch64_shrn2<mode>_insn_be): Likewise.
(aarch64_rshrn2<mode>_insn_le): Likewise.
(aarch64_rshrn2<mode>_insn_be): Likewise.
gcc/testsuite/ChangeLog:
PR target/99437
* gcc.target/aarch64/simd/pr99437.c: New test.
next prev parent reply other threads:[~2021-03-08 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 23:09 [Bug target/99437] New: " raj.khem at gmail dot com
2021-03-06 23:13 ` [Bug target/99437] " raj.khem at gmail dot com
2021-03-07 0:07 ` [Bug target/99437] [11 Regression] " pinskia at gcc dot gnu.org
2021-03-07 0:29 ` pinskia at gcc dot gnu.org
2021-03-07 14:04 ` ktkachov at gcc dot gnu.org
2021-03-08 15:06 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-08 18:57 ` raj.khem at gmail dot com
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-99437-4-RfubB3GGPD@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).