public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: pan2.li@intel.com, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, yanzhang.wang@intel.com, kito.cheng@gmail.com
Subject: Re: [PATCH v1] RISC-V: Refactor RVV class by frm_op_type template arg
Date: Mon, 21 Aug 2023 09:04:15 -0600	[thread overview]
Message-ID: <b4cdeeda-72af-8881-a9b8-4f79a62817ff@gmail.com> (raw)
In-Reply-To: <20230818025355.3280223-1-pan2.li@intel.com>



On 8/17/23 20:53, Pan Li via Gcc-patches wrote:
> From: Pan Li <pan2.li@intel.com>
> 
> As suggested by kito, we will add new frm_opt_type template arg
> to the op class, to avoid the duplicated function expand.
> 
> Signed-off-by: Pan Li <pan2.li@intel.com>
> 
> gcc/ChangeLog:
> 
> 	* config/riscv/riscv-vector-builtins-bases.cc
> 	(class binop_frm): Removed.
> 	(class reverse_binop_frm): Ditto.
> 	(class widen_binop_frm): Ditto.
> 	(class vfmacc_frm): Ditto.
> 	(class vfnmacc_frm): Ditto.
> 	(class vfmsac_frm): Ditto.
> 	(class vfnmsac_frm): Ditto.
> 	(class vfmadd_frm): Ditto.
> 	(class vfnmadd_frm): Ditto.
> 	(class vfmsub_frm): Ditto.
> 	(class vfnmsub_frm): Ditto.
> 	(class vfwmacc_frm): Ditto.
> 	(class vfwnmacc_frm): Ditto.
> 	(class vfwmsac_frm): Ditto.
> 	(class vfwnmsac_frm): Ditto.
> 	(class unop_frm): Ditto.
> 	(class vfrec7_frm): Ditto.
> 	(class binop): Add frm_op_type template arg.
> 	(class unop): Ditto.
> 	(class widen_binop): Ditto.
> 	(class widen_binop_fp): Ditto.
> 	(class reverse_binop): Ditto.
> 	(class vfmacc): Ditto.
> 	(class vfnmsac): Ditto.
> 	(class vfmadd): Ditto.
> 	(class vfnmsub): Ditto.
> 	(class vfnmacc): Ditto.
> 	(class vfmsac): Ditto.
> 	(class vfnmadd): Ditto.
> 	(class vfmsub): Ditto.
> 	(class vfwmacc): Ditto.
> 	(class vfwnmacc): Ditto.
> 	(class vfwmsac): Ditto.
> 	(class vfwnmsac): Ditto.
> 	(class float_misc): Ditto.
So in the expand method, you added a case for OP_TYPE_vx.  I assume that 
was intentional -- but it's not mentioned anywhere in the ChangeLog.  So 
please update the ChangeLog if it was intentional or remove the change 
if it wasn't intentional.  Pre-approved with whichever change is 
appropriate.

Thanks,
Jeff

  reply	other threads:[~2023-08-21 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  2:53 pan2.li
2023-08-21 15:04 ` Jeff Law [this message]
2023-08-21 15:07   ` Kito Cheng
2023-08-22  0:09     ` Li, Pan2
2023-08-24  5:03       ` Li, Pan2
2023-08-22  4:19 ` [PATCH v2] " pan2.li
2023-08-24  7:44   ` Kito Cheng
2023-08-24  7:53     ` Li, Pan2

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=b4cdeeda-72af-8881-a9b8-4f79a62817ff@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=pan2.li@intel.com \
    --cc=yanzhang.wang@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).