From: James Greenhalgh <james.greenhalgh@arm.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <nd@arm.com>, <ramana.radhakrishnan@arm.com>, <kyrtka01@arm.com>,
<richard.earnshaw@arm.com>, <nickc@redhat.com>
Subject: [Patch ARM] Fix PR71778
Date: Mon, 12 Jun 2017 13:58:00 -0000 [thread overview]
Message-ID: <1497275869-1612-1-git-send-email-james.greenhalgh@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi,
PR71778 is an ICE when you pass a non-constant argument to an intrinsic
which requires a constant.
This ICE was introduced after we rewrote some of the builtin handling for
Neon intrinsics, the issue is that after throwing an error in
arm_expand_builtin_args, we return const0_rtx to indicate the expand
has failed
if (!(*insn_data[icode].operand[opno].predicate)
(op[argc], mode[argc]))
{
error ("%Kargument %d must be a constant immediate",
exp, argc + 1);
return const0_rtx;
}
At this point we're safely in to invalid code, but the mid-end continues
trying to resolve the assignment, with const0_rtx on the right-hand
side. That gets in to trouble in movv2di, which sees the constant and
tries to expand through neon_make_constant, which doesn't expect to see
a const0_rtx in the assignment (it wants a vector), and we hit a
gcc_unreachable () and take the ICE.
There are a few moving parts in the back end, so it isn't clear to me that
the fix I've come up with is 100% in the right place. AArch64 doesn't
bother with a similar construct, expanding straight to a mov with whatever
you've given it, so I don't see a right place over there.
The change is defensible, but I don't really know the ARM back end.
Bootstrapped on arm-none-linux-gnueabihf.
OK?
Thanks,
James
---
gcc/
2017-06-12 James Greenhalgh <james.greenhalgh@arm.com>
PR target/71778
* config/arm/arm.c (neon_make_constant): Return const0_rtx for
const0_rtx input.
gcc/testsuite/
2017-06-12 James Greenhalgh <james.greenhalgh@arm.com>
PR target/71778
* gcc.target/arm/pr71778.c: New.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Patch-ARM-Fix-PR71778.patch --]
[-- Type: text/x-patch; name="0001-Patch-ARM-Fix-PR71778.patch", Size: 1533 bytes --]
diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index e503891..b8d59c6 100644
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -12124,6 +12124,11 @@ neon_make_constant (rtx vals)
if (n_const == n_elts)
const_vec = gen_rtx_CONST_VECTOR (mode, XVEC (vals, 0));
}
+ else if (vals == const0_rtx)
+ /* Something invalid, perhaps from expanding an intrinsic
+ which requires a constant argument, where a variable argument
+ was passed. */
+ return const0_rtx;
else
gcc_unreachable ();
diff --git a/gcc/testsuite/gcc.target/arm/pr71778.c b/gcc/testsuite/gcc.target/arm/pr71778.c
new file mode 100644
index 0000000..d5b0d04
--- /dev/null
+++ b/gcc/testsuite/gcc.target/arm/pr71778.c
@@ -0,0 +1,24 @@
+/* { dg-do compile } */
+/* { dg-require-effective-target arm_neon_ok } */
+/* { dg-options "-O2" } */
+/* { dg-add-options arm_neon } */
+
+typedef __simd128_int32_t int32x4_t;
+
+__extension__ extern __inline int32x4_t
+__attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
+vshrq_n_s32 (int32x4_t __a, const int __b)
+{
+ /* Errors for arm_neon.h intrinsics using constants end up on the line
+ in arm_neon.h rather than the source file line. That means we
+ need to put the dg-error up here, rather than on line 22 where we'd
+ like it. */
+ return (int32x4_t)__builtin_neon_vshrs_nv4si (__a, __b); /* { dg-error "argument 2 must be a constant immediate" } */
+}
+
+int32x4_t
+shift (int32x4_t a, int b)
+{
+ return vshrq_n_s32 (a, b);
+}
+
next reply other threads:[~2017-06-12 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 13:58 James Greenhalgh [this message]
2017-06-14 10:21 ` Kyrill Tkachov
2017-06-16 9:07 ` James Greenhalgh
2017-06-16 10:07 ` Kyrill Tkachov
2017-06-19 16:17 ` James Greenhalgh
2017-06-19 16:25 ` Kyrill Tkachov
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=1497275869-1612-1-git-send-email-james.greenhalgh@arm.com \
--to=james.greenhalgh@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrtka01@arm.com \
--cc=nd@arm.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
/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).