From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc-patches@gcc.gnu.org, WANG Xuerui <i@xen0n.name>,
Chenghua Xu <xuchenghua@loongson.cn>,
Yujie Yang <yangyujie@loongson.cn>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [PATCH 0/2] LoongArch: testsuite: Fix tests related to stack
Date: Mon, 6 Mar 2023 09:15:27 +0800 [thread overview]
Message-ID: <9b7181b2-00b5-9fd1-316e-979cf580e6e1@loongson.cn> (raw)
In-Reply-To: <ef648d8a32758563f2cf0c94cafb232b93386d51.camel@xry111.site>
在 2023/3/6 上午12:21, Xi Ruoyao 写道:
> On Fri, 2023-03-03 at 08:21 -0800, Mike Stump wrote:
>> On Mar 3, 2023, at 12:40 AM, Xi Ruoyao via Gcc-patches
>> <gcc-patches@gcc.gnu.org> wrote:
>>> Some trivial test case fixes. Ok for trunk?
>> Ok.
> Lulu: if you don't object I'll push these two in this week.
>
> I tried to bisect for the exact point where the test cases are broken,
> but it turns out they are broken the first day committed (r13-4401). As
> the draft of r13-4401 was sent in Sept 2022 but it's committed in Nov
> 2022, I can only guess something had changed in the two months and broke
> the tests...
Sorry for the late reply, the first patch I think is fine. But I haven't
reproduced the problem of the second mail.
Is there any special option in the configuration?
next prev parent reply other threads:[~2023-03-06 1:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 8:40 Xi Ruoyao
2023-03-03 8:40 ` [PATCH 1/2] LoongArch: testsuite: Disable stack protector for some tests Xi Ruoyao
2023-03-03 8:40 ` [PATCH 2/2] LoongArch: testsuite: Adjust stack offsets in stack-check-cfa tests Xi Ruoyao
2023-03-03 16:21 ` [PATCH 0/2] LoongArch: testsuite: Fix tests related to stack Mike Stump
2023-03-05 16:21 ` Xi Ruoyao
2023-03-06 1:15 ` Lulu Cheng [this message]
2023-03-06 2:48 ` Xi Ruoyao
2023-03-06 3:16 ` Xi Ruoyao
2023-03-06 5:59 ` Xi Ruoyao
2023-03-06 8:02 ` Xi Ruoyao
2023-03-06 8:12 ` Lulu Cheng
2023-03-06 8:18 ` Xi Ruoyao
2023-03-06 8:22 ` Lulu Cheng
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=9b7181b2-00b5-9fd1-316e-979cf580e6e1@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=mikestump@comcast.net \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
--cc=yangyujie@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).