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/108589] ICE: RTL check: expected code 'reg', have 'subreg' in rhs_regno, at rtl.h:1932 with -mtune=ampere1a -fno-split-wide-types Date: Tue, 18 Apr 2023 00:09:39 +0000 [thread overview] Message-ID: <bug-108589-4-BdMAdCHHc4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108589-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108589 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Philipp Tomsich <ptomsich@gcc.gnu.org>: https://gcc.gnu.org/g:b54061569221e678e99e9e49dc0ac79228d9c407 commit r11-10634-gb54061569221e678e99e9e49dc0ac79228d9c407 Author: Philipp Tomsich <philipp.tomsich@vrull.eu> Date: Mon Jan 30 23:40:26 2023 +0100 PR target/108589 - Check REG_P for AARCH64_FUSE_ADDSUB_2REG_CONST1 This adds a check for REG_P on SET_DEST for the new idiom recognizer for AARCH64_FUSE_ADDSUB_2REG_CONST1. The reported ICE is only observable with checking=rtl. Bootstrapped/regtested aarch64-linux, committed. PR target/108589 gcc/ChangeLog: * config/aarch64/aarch64.c (aarch_macro_fusion_pair_p): Check REG_P on SET_DEST. gcc/testsuite/ChangeLog: * gcc.target/aarch64/pr108589.c: New test. (cherry picked from commit a39c6ec97906766ad65d15d4856fd41121ee7a45)
next prev parent reply other threads:[~2023-04-18 0:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-29 8:40 [Bug target/108589] New: " zsojka at seznam dot cz 2023-01-30 4:26 ` [Bug target/108589] " pinskia at gcc dot gnu.org 2023-01-30 11:08 ` ptomsich at gcc dot gnu.org 2023-01-30 22:11 ` ptomsich at gcc dot gnu.org 2023-01-31 15:34 ` cvs-commit at gcc dot gnu.org 2023-04-18 0:08 ` cvs-commit at gcc dot gnu.org 2023-04-18 0:09 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-18 0:38 ` cvs-commit at gcc dot gnu.org 2023-05-09 8:26 ` ptomsich 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-108589-4-BdMAdCHHc4@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).