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/104662] arm: ice in simd_valid_immediate Date: Thu, 24 Feb 2022 14:34:58 +0000 [thread overview] Message-ID: <bug-104662-4-iO0S3w0bZ7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104662-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104662 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #1 from Christophe Lyon <clyon at gcc dot gnu.org> --- Hello, Do you mean you are running 'make check' with a cross-gcc configure with --target arm-linux-gnueabif and you see this failure? On my side, 'make check' shows no error on this test. Given the flags you show, it seems you are in fact compiling the testcase by hand, effectively not including the mandatory -march=armv8.1-m.main+mve? V*BI types require MVE, so the test is not supposed to run without this option. However, this small change avoids the ICE: diff --git a/gcc/config/arm/arm.cc b/gcc/config/arm/arm.cc index c1103d9..5adc45b 100644 --- a/gcc/config/arm/arm.cc +++ b/gcc/config/arm/arm.cc @@ -12811,6 +12811,9 @@ simd_valid_immediate (rtx op, machine_mode mode, int inverse, || n_elts * innersize != 16)) return -1; + if (!TARGET_HAVE_MVE && (GET_MODE_CLASS (mode) == MODE_VECTOR_BOOL)) + return -1; + /* Vectors of float constants. */ if (GET_MODE_CLASS (mode) == MODE_VECTOR_FLOAT) {
next prev parent reply other threads:[~2022-02-24 14:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 13:38 [Bug target/104662] New: " dcb314 at hotmail dot com 2022-02-24 14:34 ` clyon at gcc dot gnu.org [this message] 2022-02-24 14:38 ` [Bug target/104662] " jakub at gcc dot gnu.org 2022-04-25 9:24 ` clyon at gcc dot gnu.org 2022-05-04 8:19 ` cvs-commit at gcc dot gnu.org 2022-05-04 8:23 ` clyon 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-104662-4-iO0S3w0bZ7@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).