From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Hui Li <lihui@loongson.cn>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: LoongArch: Handle special struct in dummy call
Date: Wed, 11 Oct 2023 09:13:54 +0800 [thread overview]
Message-ID: <ec1f410f-f6f3-a5e6-0055-f1f5f37b404e@loongson.cn> (raw)
In-Reply-To: <20231008073244.17594-1-lihui@loongson.cn>
On 10/08/2023 03:32 PM, Hui Li wrote:
> When execute the following command on LoongArch:
>
> make check-gdb TESTS="gdb.base/infcall-nested-structs-c++.exp"
>
> there exist some failed testcases:
>
> === gdb Summary ===
>
> # of expected passes 5533
> # of unexpected failures 367
>
> The root cause is related with a struct containing floating-point
> members as function argument or return value for a dummy call.
...
>
> With this patch, there are no failed testcases:
>
> make check-gdb TESTS="gdb.base/infcall-nested-structs-c++.exp"
>
> === gdb Summary ===
>
> # of expected passes 5900
>
> Signed-off-by: Hui Li <lihui@loongson.cn>
Thanks for the patch, looks good to me.
Tested on LoongArch, pushed.
Thanks,
Tiezhu
prev parent reply other threads:[~2023-10-11 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 7:32 Hui Li
2023-10-11 1:13 ` Tiezhu Yang [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=ec1f410f-f6f3-a5e6-0055-f1f5f37b404e@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=gdb-patches@sourceware.org \
--cc=lihui@loongson.cn \
/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).