From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"cel@linux.ibm.com" <cel@linux.ibm.com>
Subject: Re: [PATCH] rs6000, unwind-on-each-instruction fix.
Date: Mon, 12 Feb 2024 09:55:04 +0000 [thread overview]
Message-ID: <04d36bd8b0155ace0b8930beaec9f8d786738863.camel@de.ibm.com> (raw)
In-Reply-To: <c3b8473d-0326-4186-a7ec-15841ce258a9@linux.ibm.com>
Carl Love <cel@linux.ibm.com> wrote:
>rs6000, unwind-on-each-instruction fix.
>
>The function rs6000_epilogue_frame_cache assumes the LR and gprs have been
>restored. In fact register r31 and the link register, lr, may not have
>been restored yet. This patch adds support to store the lr and gpr
>register unrolling rules in the cache. The LR and GPR values can now be
>unrolled correctly.
>
>Patch fixes all 10 regresion test failures for the unwind-on-each-insn.exp.
This is OK (with the cosmetic fix pointed out by Tom).
Thanks,
Ulrich
prev parent reply other threads:[~2024-02-12 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 21:35 Carl Love
2024-02-08 16:23 ` PING " Carl Love
2024-02-08 18:55 ` Tom Tromey
2024-02-08 19:37 ` Carl Love
2024-02-12 9:55 ` Ulrich Weigand [this message]
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=04d36bd8b0155ace0b8930beaec9f8d786738863.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.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).