From: WANG Xuerui <i@xen0n.name>
To: Lulu Cheng <chenglulu@loongson.cn>, Guo Jie <guojie@loongson.cn>,
Xi Ruoyao <xry111@xry111.site>,
gcc-patches@gcc.gnu.org
Cc: Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: [PATCH] LoongArch: Enable shrink wrapping
Date: Wed, 26 Apr 2023 18:21:23 +0800 [thread overview]
Message-ID: <a25e2c86-f7da-68ca-3a82-20e44e3244c9@xen0n.name> (raw)
In-Reply-To: <b24f9149-d7ee-b6ba-7e02-01d7a09aa8c5@loongson.cn>
On 2023/4/26 18:14, Lulu Cheng wrote:
>
> 在 2023/4/26 下午6:02, WANG Xuerui 写道:
>>
>> On 2023/4/26 17:53, Lulu Cheng wrote:
>>> Hi, ruoyao:
>>>
>>> The performance of spec2006 is finished. The fixed-point
>>> 400.perlbench has about 3% performance improvement,
>>>
>>> and the other basics have not changed, and the floating-point tests
>>> have basically remained the same.
>> Nice to know!
>>>
>>> Do you have any questions about the test cases mentioned by
>>> Guo Jie? If there is no problem, modify the test case,
>>>
>>> I think the code can be merged into the main branch.
>>>
>>> <snip>
>> BTW what about the previous function/loop alignment patches? The LLVM
>> changes are also waiting for such results. ;-)
> Well, there are many combinations in this align test, so the test time
> will be very long. I will reply the result as soon as the test results
> come out.:-)
>
Oh, I got. Thanks very much for all the tests and take your time!
next prev parent reply other threads:[~2023-04-26 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 13:19 Xi Ruoyao
2023-04-24 8:51 ` Lulu Cheng
2023-04-25 7:37 ` Lulu Cheng
2023-04-25 9:12 ` Guo Jie
2023-04-26 9:53 ` Lulu Cheng
2023-04-26 10:02 ` WANG Xuerui
2023-04-26 10:14 ` Lulu Cheng
2023-04-26 10:21 ` WANG Xuerui [this message]
2023-05-06 17:07 ` Xi Ruoyao
2023-05-06 23:34 ` chenglulu
2023-04-26 13:29 ` Xi Ruoyao
2023-05-06 17:05 ` Pushed: [PATCH v2] " Xi Ruoyao
2023-05-06 23:40 ` chenglulu
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=a25e2c86-f7da-68ca-3a82-20e44e3244c9@xen0n.name \
--to=i@xen0n.name \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojie@loongson.cn \
--cc=xry111@xry111.site \
--cc=xuchenghua@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).