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/105257] [8/9/10/11 regression] ICE in final_scan_insn_1, at final.cc:2811 Date: Thu, 21 Apr 2022 09:30:04 +0000 [thread overview] Message-ID: <bug-105257-4-M0wmzwE51C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105257-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105257 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:dfe099b4b5c0077a6bd699912fe9442431239e39 commit r11-9898-gdfe099b4b5c0077a6bd699912fe9442431239e39 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 19 18:58:59 2022 +0200 sparc: Preserve ORIGINAL_REGNO in epilogue_renumber [PR105257] The following testcase ICEs, because the pic register is (reg:DI 24 %i0 [109]) and is used in the delay slot of a return. We invoke epilogue_renumber and that changes it to (reg:DI 8 %o0) which no longer satisfies sparc_pic_register_p predicate, so we don't recognize the insn anymore. The following patch fixes that by preserving ORIGINAL_REGNO if specified, so we get (reg:DI 8 %o0 [109]) instead. 2022-04-19 Jakub Jelinek <jakub@redhat.com> PR target/105257 * config/sparc/sparc.c (epilogue_renumber): If ORIGINAL_REGNO, use gen_raw_REG instead of gen_rtx_REG and copy over also ORIGINAL_REGNO. Use return 0; instead of /* fallthrough */. * gcc.dg/pr105257.c: New test. (cherry picked from commit eeca2b8bd03f57c59c6cf48bf6b9bd6dc86924f6)
next prev parent reply other threads:[~2022-04-21 9:30 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 8:23 [Bug target/105257] New: [8/9/10/11/12 " ro at gcc dot gnu.org 2022-04-13 8:23 ` [Bug target/105257] " ro at gcc dot gnu.org 2022-04-19 9:08 ` jakub at gcc dot gnu.org 2022-04-19 9:18 ` jakub at gcc dot gnu.org 2022-04-19 10:14 ` ebotcazou at gcc dot gnu.org 2022-04-19 10:20 ` ebotcazou at gcc dot gnu.org 2022-04-19 10:29 ` jakub at gcc dot gnu.org 2022-04-19 10:40 ` ebotcazou at gcc dot gnu.org 2022-04-19 15:31 ` rguenth at gcc dot gnu.org 2022-04-19 16:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-04-19 17:03 ` cvs-commit at gcc dot gnu.org 2022-04-19 17:06 ` [Bug target/105257] [8/9/10/11 " jakub at gcc dot gnu.org 2022-04-21 9:30 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-21 9:31 ` [Bug target/105257] [8/9/10 " jakub at gcc dot gnu.org 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-06 8:56 ` [Bug target/105257] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:26 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:26 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` 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-105257-4-M0wmzwE51C@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).