From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, Guo Jie <guojie@loongson.cn>,
gcc-patches@gcc.gnu.org
Cc: xuchenghua@loongson.cn, i@xen0n.name
Subject: Re:[pushed] [PATCH] LoongArch: Enable -fsched-pressure by default at -O1 and higher.
Date: Fri, 8 Sep 2023 17:54:47 +0800 [thread overview]
Message-ID: <3909268e-735c-aee2-9e89-1c7991bb6785@loongson.cn> (raw)
In-Reply-To: <8b98f5a1716e84f4e380246b243debc7b21e3288.camel@xry111.site>
Pushed to r14-3805.
在 2023/9/8 下午4:32, Xi Ruoyao 写道:
> On Fri, 2023-09-08 at 16:29 +0800, Guo Jie wrote:
>> Hi,
>>
>> What I wanna change is "gcc/common/config/loongarch/loongarch-
>> common.cc",
>>
>> and the patch is automatically generated by "git gcc-commit-mklog".
>>
>> Is it necessary to to remove "common/" ?
> My bad. I didn't realized the file has been moved to common.
>
> Don't change it :(.
>
>> Thanks for the review.
>>
>>
>> 在 2023/9/8 下午4:06, Xi Ruoyao 写道:
>>> On Fri, 2023-09-08 at 10:00 +0800, Guo Jie wrote:
>>>> gcc/ChangeLog:
>>>>
>>>> * common/config/loongarch/loongarch-common.cc:
>>> "common/" should be removed. You can use "git gcc-verify" to figure
>>> out
>>> this kind of error before sending a patch in the future.
>>>
>>>> (default_options loongarch_option_optimization_table):
>>>> Default to -fsched-pressure.
>>> "Default to -fsched-pressure at -O1 or above."
>>>
>>> Otherwise OK.
>>>
>>>> ---
>>>> gcc/common/config/loongarch/loongarch-common.cc | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/gcc/common/config/loongarch/loongarch-common.cc
>>>> b/gcc/common/config/loongarch/loongarch-common.cc
>>>> index c5ed37d27a6..b6901910b70 100644
>>>> --- a/gcc/common/config/loongarch/loongarch-common.cc
>>>> +++ b/gcc/common/config/loongarch/loongarch-common.cc
>>>> @@ -36,6 +36,7 @@ static const struct default_options
>>>> loongarch_option_optimization_table[] =
>>>> { OPT_LEVELS_ALL, OPT_fasynchronous_unwind_tables, NULL, 1 },
>>>> { OPT_LEVELS_1_PLUS, OPT_fsection_anchors, NULL, 1 },
>>>> { OPT_LEVELS_2_PLUS, OPT_free, NULL, 1 },
>>>> + { OPT_LEVELS_1_PLUS, OPT_fsched_pressure, NULL, 1 },
>>>> { OPT_LEVELS_NONE, 0, NULL, 0 }
>>>> };
>>>>
prev parent reply other threads:[~2023-09-08 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 2:00 Guo Jie
2023-09-08 8:06 ` Xi Ruoyao
2023-09-08 8:29 ` Guo Jie
2023-09-08 8:32 ` Xi Ruoyao
2023-09-08 9:54 ` chenglulu [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=3909268e-735c-aee2-9e89-1c7991bb6785@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojie@loongson.cn \
--cc=i@xen0n.name \
--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).