public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vvinayag at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100757] [12 Regression] arm: ICE (unrecognizable insn) with MVE VPSELQ_S since r12-834-ga6eacbf10
Date: Wed, 20 Oct 2021 10:07:54 +0000 [thread overview]
Message-ID: <bug-100757-4-fAiJi7w73B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100757-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100757
vvinayag at arm dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vvinayag at arm dot com
--- Comment #14 from vvinayag at arm dot com ---
(In reply to Christophe Lyon from comment #12)
> Yes, I've been working on it for a while, it's proving to be a bit tricky
> when switching to HImode as suggested by Richard. I have something working,
> now checking I haven't broken Neon.
Hi Christophe, if you are working on this, just wondering whether we are close
to getting a patch for this, thank you.
next prev parent reply other threads:[~2021-10-20 10:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 16:26 [Bug target/100757] New: arm: ICE (unrecognizable insn) with MVE VPSELQ_S acoplan at gcc dot gnu.org
2021-05-25 16:36 ` [Bug target/100757] [12 Regression] " clyon at gcc dot gnu.org
2021-05-25 16:37 ` acoplan at gcc dot gnu.org
2021-05-26 7:51 ` rguenth at gcc dot gnu.org
2021-05-26 8:55 ` [Bug target/100757] [12 Regression] arm: ICE (unrecognizable insn) with MVE VPSELQ_S since r12-834-ga6eacbf10 acoplan at gcc dot gnu.org
2021-05-26 9:01 ` clyon at gcc dot gnu.org
2021-05-26 9:06 ` acoplan at gcc dot gnu.org
2021-05-26 16:02 ` clyon at gcc dot gnu.org
2021-05-26 16:09 ` acoplan at gcc dot gnu.org
2021-05-26 21:10 ` clyon at gcc dot gnu.org
2021-06-04 11:51 ` acoplan at gcc dot gnu.org
2021-06-04 14:18 ` clyon at gcc dot gnu.org
2021-07-01 13:40 ` acoplan at gcc dot gnu.org
2021-07-01 13:48 ` clyon at gcc dot gnu.org
2021-08-16 12:33 ` clyon at gcc dot gnu.org
2021-10-20 10:07 ` vvinayag at arm dot com [this message]
2021-10-20 11:19 ` clyon at gcc dot gnu.org
2022-01-17 14:40 ` rguenth at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 16:07 ` clyon at gcc dot gnu.org
2022-02-23 6:44 ` cvs-commit 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-100757-4-fAiJi7w73B@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).