public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Demin Han <demin.han@starfivetech.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: pan2.li <pan2.li@intel.com>
Subject: Re: [PATCH] RISC-V: Fix calculation of max live vregs
Date: Thu, 21 Dec 2023 09:47:43 +0800	[thread overview]
Message-ID: <2c593804-1dd8-4ae4-a5d2-048561537ce8@starfivetech.com> (raw)
In-Reply-To: <1f44e02c-fffe-4150-86d0-c0e696ae0ec8@gmail.com>

Hi Jeff,

Thanks for reminding this.
Regression test info will be added to commit log in following patches.

Demin

On 2023/12/20 23:28, Jeff Law wrote:
> 
> 
> On 12/20/23 04:17, juzhe.zhong@rivai.ai wrote:
>> I see. LGTM. Thanks for explanation.
>>
>> I will ask Li Pan commit it for you.
> The patch from Demin didn't specify if it had been regression tested.
> 
> All patches must be regression tested and an indication that the test passed and on what target must be included in the patch email thread.
> 
> Please don't ACK patches that haven't followed this policy. It's OK with conditions like "OK after verifying this patch doesn't cause regressions in the testsuite on rv64gc" or something similar.
> 
> jeff

      parent reply	other threads:[~2023-12-21  1:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  8:15 demin.han
2023-12-20  9:56 ` juzhe.zhong
2023-12-20 11:10   ` Demin Han
2023-12-20 11:17     ` juzhe.zhong
2023-12-20 11:20       ` Li, Pan2
2023-12-20 15:28       ` Jeff Law
2023-12-20 15:30         ` 钟居哲
2023-12-21  1:47         ` Demin Han [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=2c593804-1dd8-4ae4-a5d2-048561537ce8@starfivetech.com \
    --to=demin.han@starfivetech.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=pan2.li@intel.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).