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/96072] [10/11/12 Regression] ICE: Segmentation fault (in add_reg_note) Date: Wed, 19 Oct 2022 09:05:23 +0000 [thread overview] Message-ID: <bug-96072-4-neKb2IpuMg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96072-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96072 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:c7f17493cc26a4395d549547075603a15f4c94a7 commit r12-8846-gc7f17493cc26a4395d549547075603a15f4c94a7 Author: Kewen Lin <linkw@linux.ibm.com> Date: Mon Sep 26 00:33:18 2022 -0500 rs6000: Fix the condition with frame_pointer_needed_indeed [PR96072] As PR96072 shows, the code adding REG_CFA_DEF_CFA reg note makes one assumption that we have emitted one insn which restores the frame pointer previously. That part of code was guarded with flag frame_pointer_needed before, it was consistent, but it was replaced with flag frame_pointer_needed_indeed since commit r10-7981. It caused ICE due to unexpected NULL insn. PR target/96072 gcc/ChangeLog: * config/rs6000/rs6000-logue.cc (rs6000_emit_epilogue): Update the condition for adding REG_CFA_DEF_CFA reg note with frame_pointer_needed_indeed. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr96072.c: New test. (cherry picked from commit 5be0950d22209f5ba69d244387228e12389a8470)
next prev parent reply other threads:[~2022-10-19 9:05 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-06 4:47 [Bug target/96072] New: " asolokha at gmx dot com 2020-08-11 4:13 ` [Bug target/96072] " asolokha at gmx dot com 2020-08-19 7:30 ` asolokha at gmx dot com 2022-09-13 22:25 ` segher at gcc dot gnu.org 2022-09-14 2:33 ` asolokha at gmx dot com 2022-09-14 12:20 ` linkw at gcc dot gnu.org 2022-09-14 12:23 ` linkw at gcc dot gnu.org 2022-09-15 5:44 ` [Bug target/96072] [10/11/12 Regression] " linkw at gcc dot gnu.org 2022-09-26 5:34 ` cvs-commit at gcc dot gnu.org 2022-10-19 9:05 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-19 11:24 ` cvs-commit at gcc dot gnu.org 2022-10-20 2:16 ` cvs-commit at gcc dot gnu.org 2022-10-20 2:28 ` linkw 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-96072-4-neKb2IpuMg@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).