public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter
Date: Tue, 17 Oct 2023 13:12:52 +0000 [thread overview]
Message-ID: <bug-111753-4-OxP29Ly5Ws@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111753-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2023-10-17
Status|UNCONFIRMED |NEW
Priority|P3 |P1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
next prev parent reply other threads:[~2023-10-17 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 4:59 [Bug rtl-optimization/111753] New: " zsojka at seznam dot cz
2023-10-10 9:18 ` [Bug rtl-optimization/111753] " rguenth at gcc dot gnu.org
2023-10-17 13:12 ` rguenth at gcc dot gnu.org [this message]
2023-10-18 14:15 ` [Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499 jakub at gcc dot gnu.org
2023-10-19 5:49 ` haochen.jiang at intel dot com
2023-10-20 6:21 ` haochen.jiang at intel dot com
2023-10-23 2:02 ` cvs-commit at gcc dot gnu.org
2023-10-23 2:03 ` haochen.jiang at intel dot com
2023-10-23 2:34 ` sjames 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-111753-4-OxP29Ly5Ws@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).