public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96072] ICE: Segmentation fault (in add_reg_note) Date: Wed, 14 Sep 2022 12:20:28 +0000 [thread overview] Message-ID: <bug-96072-4-6ELwCnD7jV@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 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linkw at gcc dot gnu.org Status|WAITING |NEW --- Comment #5 from Kewen Lin <linkw at gcc dot gnu.org> --- Confirmed. if (DEFAULT_ABI == ABI_V4 || flag_shrink_wrap) { /* If the frame pointer was used then we can't delay emitting a REG_CFA_DEF_CFA note. This must happen on the insn that restores the frame pointer, r31. We may have already emitted a REG_CFA_DEF_CFA note, but that's OK; A duplicate is discarded by dwarf2cfi.cc/dwarf2out.cc, and in any case would be harmless if emitted. */ if (frame_pointer_needed) { insn = get_last_insn (); add_reg_note (insn, REG_CFA_DEF_CFA, plus_constant (Pmode, frame_reg_rtx, frame_off)); RTX_FRAME_RELATED_P (insn) = 1; } ICE since the insn here is (rtx) 0x0. I think the code here has the assumption that the frame pointer restoring happened ahead, it's: /* If we have a frame pointer, we can restore the old stack pointer from it. */ else if (frame_pointer_needed_indeed) { frame_reg_rtx = sp_reg_rtx; ....
next prev parent reply other threads:[~2022-09-14 12:20 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 [this message] 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 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-6ELwCnD7jV@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).