public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ARM/heads/gcs-13)] aarch64: Do not force a stack frame for EH returns
Date: Wed, 14 Feb 2024 15:35:11 +0000 (GMT)	[thread overview]
Message-ID: <20240214153511.64020385E456@sourceware.org> (raw)

https://gcc.gnu.org/g:f6d55bdfef950282f2fc2a15dbda3dbfd324e876

commit f6d55bdfef950282f2fc2a15dbda3dbfd324e876
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Tue May 9 11:07:05 2023 +0100

    aarch64: Do not force a stack frame for EH returns
    
    EH returns no longer rely on clobbering the return address on the stack
    so forcing a stack frame is not necessary.
    
    This does not actually change the code gen for the unwinder since there
    are calls before the EH return.
    
    gcc/ChangeLog:
    
            * config/aarch64/aarch64.cc (aarch64_needs_frame_chain): Do not
            force frame chain for eh_return.
    
    (cherry picked from commit aa2ad77a9b3994fb679e5295d9570f6f8696540d)

Diff:
---
 gcc/config/aarch64/aarch64.cc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 0367d5dc2ef0..06aef1bb725c 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -8379,8 +8379,7 @@ aarch64_output_probe_sve_stack_clash (rtx base, rtx adjustment,
 static bool
 aarch64_needs_frame_chain (void)
 {
-  /* Force a frame chain for EH returns so the return address is at FP+8.  */
-  if (frame_pointer_needed || crtl->calls_eh_return)
+  if (frame_pointer_needed)
     return true;
 
   /* A leaf function cannot have calls or write LR.  */

                 reply	other threads:[~2024-02-14 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240214153511.64020385E456@sourceware.org \
    --to=nsz@gcc.gnu.org \
    --cc=gcc-cvs@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).