public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineetg@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	Robin Dapp <rdapp.gcc@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	palmer <palmer@dabbelt.com>, Kito Cheng <kito.cheng@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: [PATCH] RISC-V: Enable pressure-aware scheduling by default.
Date: Fri, 18 Aug 2023 16:24:07 -0700	[thread overview]
Message-ID: <e279b3ad-ccc4-6be9-f4a4-5f5baea03892@rivosinc.com> (raw)
In-Reply-To: <04b8f9ee-31f6-d699-7acc-acfa1b9102e5@gmail.com>



On 8/18/23 16:08, Jeff Law wrote:
>> There is some slight regression in code quality for a number of
>> vector tests where we spill more due to different instructions order.
>> The ones I looked at were a mix of bad luck and/or brittle tests.
>> Comparing the size of the generated assembly or the number of vsetvls
>> for SPECint also didn't show any immediate benefit but that's obviously
>> not a very fine-grained analysis.
> Yea.  In fact I wouldn't really expect significant changes other than 
> those key loops in x264.

Care to elaborate a bit more please. I've seen severe reg pressure / 
spills in a bunch of others: cactu, lbm, exchange2. Is there something 
specific to x264 spills ?

>
>>
>> diff --git a/gcc/common/config/riscv/riscv-common.cc 
>> b/gcc/common/config/riscv/riscv-common.cc
>> index 4737dcd44a1..59848b21162 100644
>> --- a/gcc/common/config/riscv/riscv-common.cc
>> +++ b/gcc/common/config/riscv/riscv-common.cc
>> @@ -2017,9 +2017,11 @@ static const struct default_options 
>> riscv_option_optimization_table[] =
>>     {
>>       { 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 },

Nit2: maybe move this 1 line up to keep LEVEL_1 together, at least the 
new ones being added.

>>   #if TARGET_DEFAULT_ASYNC_UNWIND_TABLES == 1
>>       { OPT_LEVELS_ALL, OPT_fasynchronous_unwind_tables, NULL, 1 },
>>       { OPT_LEVELS_ALL, OPT_funwind_tables, NULL, 1},
>> +    /* Enable -fsched-pressure by default when optimizing.  */
>>   #endif
>>       { OPT_LEVELS_NONE, 0, NULL, 0 }
>>     };
> Shouldn't the comment move up to before the OPT_fsched_pressure line?

Yep I had the exact same first though but then thought it was something 
deeper.
Turned out to be Occam's Razor after all :-)

Thx,
-Vineet

  reply	other threads:[~2023-08-18 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 13:57 Robin Dapp
2023-08-18 23:08 ` Jeff Law
2023-08-18 23:24   ` Vineet Gupta [this message]
2023-08-19  3:23     ` Jeff Law

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=e279b3ad-ccc4-6be9-f4a4-5f5baea03892@rivosinc.com \
    --to=vineetg@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=rdapp.gcc@gmail.com \
    /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).