public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113077] [14 Regression] ICE in  dwarf2out_frame_debug_cfa_offset with `-O2 -fstack-protector-strong -fstack-clash-protection`
Date: Tue, 09 Jan 2024 09:13:43 +0000	[thread overview]
Message-ID: <bug-113077-4-QaCi73AXTH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113077-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113077

--- Comment #7 from Alex Coplan <acoplan at gcc dot gnu.org> ---
After discussing with Richard S (thanks!), I think the problem is using
REG_CFA_OFFSET in aarch64_save_callee_saves is too brittle: it is always
required to be expressed in terms of the current CFA reg instead of e.g. just
the stack pointer. Before switching to the unspec pair representation the code
in dwarf2cfi could directly interpret the RTL and could keep track of things
itself.  We can restore that behaviour with the new (unspec) representation by
using REG_FRAME_RELATED_EXPR instead (which simply gives dwarf2cfi an
alternative pattern to look at).

Testing a patch.

  parent reply	other threads:[~2024-01-09  9:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  3:44 [Bug middle-end/113077] New: " pinskia at gcc dot gnu.org
2023-12-19  3:45 ` [Bug middle-end/113077] " pinskia at gcc dot gnu.org
2023-12-19  3:47 ` pinskia at gcc dot gnu.org
2023-12-19  3:52 ` pinskia at gcc dot gnu.org
2023-12-19  9:44 ` acoplan at gcc dot gnu.org
2024-01-08 12:51 ` [Bug target/113077] " jakub at gcc dot gnu.org
2024-01-08 14:50 ` acoplan at gcc dot gnu.org
2024-01-08 15:00 ` jakub at gcc dot gnu.org
2024-01-08 15:05 ` acoplan at gcc dot gnu.org
2024-01-09  9:13 ` acoplan at gcc dot gnu.org [this message]
2024-01-09 11:30 ` acoplan at gcc dot gnu.org
2024-01-09 15:38 ` acoplan at gcc dot gnu.org
2024-01-10  9:57 ` acoplan at gcc dot gnu.org
2024-01-10 17:02 ` acoplan at gcc dot gnu.org
2024-01-11  9:39 ` acoplan at gcc dot gnu.org
2024-01-11 10:17 ` cvs-commit at gcc dot gnu.org
2024-01-11 10:19 ` acoplan 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-113077-4-QaCi73AXTH@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: link
Be 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).