From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Chenghua Xu <xuchenghua@loongson.cn>,
Weining Lu <luweining@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: [PATCH] loongarch: use -mno-check-zero-division as the default for optimized code
Date: Mon, 4 Jul 2022 14:25:23 +0800 [thread overview]
Message-ID: <d44bc063-c5d2-a87d-93f4-3e6c2c22c489@loongson.cn> (raw)
In-Reply-To: <047d4b06093d085c2fdb96e618469d3630e953dc.camel@xry111.site>
在 2022/7/3 上午11:06, Xi Ruoyao 写道:
> On Sat, 2022-07-02 at 16:35 +0800, Lulu Cheng wrote:
>> 在 2022/7/2 下午4:24, Xi Ruoyao 写道:
>>> I'll commit the patch with the hook removed after another regtest on
>>> loongarch64-linux-gnu. I just rebuilt the entire system on my
>>> 3A5000,
>>> so I need some time to set it up. Expectation time to commit is
>>> today
>>> evening or tomorrow morning.
>>>
>>> BTW I've included this patch building my system, no bad things has
>>> happened so far.
>> Ok,Thanks!:-)
> Pushed as r13-1410.
>
> How do you think about the suggestion from Richard about a backport into
> gcc-12 branch? Normally we don't backport behavior changes, but making
> 12.1 the only exception seems compelling.
I agree with you and Richard.
Thanks!
next prev parent reply other threads:[~2022-07-04 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 2:59 Xi Ruoyao
2022-06-30 6:55 ` Richard Biener
2022-07-02 7:39 ` Lulu Cheng
2022-07-02 8:24 ` Xi Ruoyao
2022-07-02 8:35 ` Lulu Cheng
2022-07-03 3:06 ` Xi Ruoyao
2022-07-04 6:25 ` Lulu Cheng [this message]
2022-07-04 6:55 ` Xi Ruoyao
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=d44bc063-c5d2-a87d-93f4-3e6c2c22c489@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=luweining@loongson.cn \
--cc=richard.guenther@gmail.com \
--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).