From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/3] PPC/PPC64 "finish" fixes
Date: Fri, 21 Apr 2023 07:40:30 -0600 [thread overview]
Message-ID: <871qkd2w1d.fsf@tromey.com> (raw)
In-Reply-To: <20230314-submit-ppc-finish-fixes-v1-0-5f2f461b52f8@adacore.com> (Tom Tromey via Gdb-patches's message of "Tue, 14 Mar 2023 07:37:15 -0600")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> We found some minor issues with "finish" on PPC and PPC64. This
Tom> series fixes some of them.
Tom> I think there are still some issues here with fixed-point types, but I
Tom> don't hae an immediate plan to look at those.
Tom> These patches have been tested using the internal AdaCore test suite.
I'm going to check these in now.
Tom
prev parent reply other threads:[~2023-04-21 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:37 Tom Tromey
2023-03-14 13:37 ` [PATCH 1/3] Handle function descriptors in call_site_target Tom Tromey
2023-03-14 13:37 ` [PATCH 2/3] Handle erroneous DW_AT_call_return_pc Tom Tromey
2023-03-24 16:10 ` Tom Tromey
2023-03-14 13:37 ` [PATCH 3/3] Use entry values for 32-bit PPC struct return Tom Tromey
2023-04-21 13:40 ` Tom Tromey [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=871qkd2w1d.fsf@tromey.com \
--to=tromey@adacore.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).