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/94435] [9/10 Regression] ICE in extract_insn, at recog.c:2294
Date: Thu, 02 Apr 2020 10:57:51 +0000 [thread overview]
Message-ID: <bug-94435-4-fOakJ7YKwe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94435-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94435
--- Comment #4 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:df562b12d90699c20923f91df48eed08ebcb572e
commit r10-7514-gdf562b12d90699c20923f91df48eed08ebcb572e
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Apr 2 12:57:11 2020 +0200
aarch64: Fix ICE due to aarch64_gen_compare_reg_maybe_ze [PR94435]
The following testcase ICEs, because aarch64_gen_compare_reg_maybe_ze emits
invalid RTL.
For y_mode [QH]Imode it expects y to be of that mode (or CONST_INT that
fits
into that mode) and x being SImode; for non-CONST_INT y it zero extends y
into SImode and compares that against x, for CONST_INT y it zero extends y
into SImode. The problem is that when the zero extended constant isn't
usable directly, it forces it into a REG, but with y_mode mode, and then
compares against y. That is wrong, because it should force it into a
SImode
REG and compare that way.
2020-04-02 Jakub Jelinek <jakub@redhat.com>
PR target/94435
* config/aarch64/aarch64.c (aarch64_gen_compare_reg_maybe_ze): For
y_mode E_[QH]Imode and y being a CONST_INT, change y_mode to
SImode.
* gcc.target/aarch64/pr94435.c: New test.
next prev parent reply other threads:[~2020-04-02 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 9:16 [Bug target/94435] New: " marxin at gcc dot gnu.org
2020-04-01 9:16 ` [Bug target/94435] " marxin at gcc dot gnu.org
2020-04-01 9:39 ` jakub at gcc dot gnu.org
2020-04-01 21:01 ` [Bug target/94435] [9/10 Regression] " pinskia at gcc dot gnu.org
2020-04-02 10:55 ` cvs-commit at gcc dot gnu.org
2020-04-02 10:57 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-02 10:59 ` cvs-commit at gcc dot gnu.org
2020-04-02 11:00 ` jakub at gcc dot gnu.org
2020-04-22 16:10 ` 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-94435-4-fOakJ7YKwe@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).