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/94286] [10 Regression] ICE: in decompose, at rtl.h:2279 with __builtin_sub_overflow() at -O -g Date: Tue, 24 Mar 2020 09:29:57 +0000 [thread overview] Message-ID: <bug-94286-4-MAhn1koLwO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94286-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94286 --- 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:596c90d35591589e0efddda65c81609fb422a986 commit r10-7352-g596c90d35591589e0efddda65c81609fb422a986 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Mar 24 10:28:58 2020 +0100 arm: Fix arm {,u}subvdi4 and usubvsi4 expanders [PR94286] The following testcase ICEs, because these expanders will happily create a SImode 0x80000000 CONST_INT, which is not valid RTL, as CONST_INTs need to be sign extended from the mode precision to full HWI. 2020-03-24 Jakub Jelinek <jakub@redhat.com> PR target/94286 * config/arm/arm.md (subvdi4, usubvsi4, usubvdi4): Use gen_int_mode instead of GEN_INT. * gcc.dg/pr94286.c: New test.
next prev parent reply other threads:[~2020-03-24 9:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 14:58 [Bug rtl-optimization/94286] New: " zsojka at seznam dot cz 2020-03-23 15:00 ` [Bug rtl-optimization/94286] " zsojka at seznam dot cz 2020-03-23 15:22 ` rguenth at gcc dot gnu.org 2020-03-23 18:21 ` [Bug target/94286] " jakub at gcc dot gnu.org 2020-03-23 18:29 ` jakub at gcc dot gnu.org 2020-03-23 19:15 ` zsojka at seznam dot cz 2020-03-24 9:29 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-24 9:37 ` 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-94286-4-MAhn1koLwO@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).