public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Andreas Krebbel via Gcc <gcc@gcc.gnu.org>
Subject: Re: CFI for saved argument registers
Date: Mon, 16 May 2022 16:39:18 +0200	[thread overview]
Message-ID: <87k0ala6eh.fsf@igel.home> (raw)
In-Reply-To: <7d266787-9a64-07e6-bf7b-1bd01119517c@linux.ibm.com> (Andreas Krebbel via Gcc's message of "Mon, 16 May 2022 08:29:32 +0200")

On Mai 16 2022, Andreas Krebbel via Gcc wrote:

> The only way I see right now is adding a new reg note to invalidate
> the save information in the reg_save array in dwarf2cfi.
>
> Would this be acceptable? Is there perhaps an easier way to achieve that?

Doesn't it work to use .cfi_remember_state/.cfi_restore_state?

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  parent reply	other threads:[~2022-05-16 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  6:29 Andreas Krebbel
2022-05-16 13:25 ` Florian Weimer
2022-05-16 14:39 ` Andreas Schwab [this message]
2022-05-17  6:19   ` Andreas Krebbel
2022-05-31 12:11 ` Andreas Krebbel

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=87k0ala6eh.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gcc@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).