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/107969] ICE in extract_insn, at recog.cc:2791 since r13-3292-gc2565a31c1622ab0
Date: Tue, 06 Dec 2022 11:17:12 +0000 [thread overview]
Message-ID: <bug-107969-4-888tO3LTIb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107969-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107969
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:bcf89f05f7b0b1732553e224548f1de55321e437
commit r13-4505-gbcf89f05f7b0b1732553e224548f1de55321e437
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Dec 6 12:16:37 2022 +0100
i386: Fix up expander conditions on cbranchbf4 and cstorebf4 [PR107969]
With -msoft-float we ICE on __bf16 comparisons, because the
insns we want to use under the hood (cbranchsf4 and cstoresf4)
after performing the fast extensions aren't available.
The following patch copies the conditions from the c*sf4 expanders
to the corresponding c*bf4 expanders.
2022-12-06 Jakub Jelinek <jakub@redhat.com>
PR target/107969
* config/i386/i386.md (cbranchbf4, cstorebf4): Guard expanders
with the same condition as cbranchsf4 or cstoresf4 expanders.
* gcc.target/i386/pr107969.c: New test.
next prev parent reply other threads:[~2022-12-06 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:47 [Bug c/107969] New: " marxin at gcc dot gnu.org
2022-12-05 8:47 ` [Bug c/107969] " marxin at gcc dot gnu.org
2022-12-05 8:56 ` [Bug target/107969] " pinskia at gcc dot gnu.org
2022-12-05 9:19 ` marxin at gcc dot gnu.org
2022-12-05 16:30 ` jakub at gcc dot gnu.org
2022-12-05 16:30 ` jakub at gcc dot gnu.org
2022-12-06 11:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-06 11:17 ` [Bug target/107969] [13 Regression] " jakub 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-107969-4-888tO3LTIb@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).