Thanks Robin.

> I assume the test expectation changes are necessary because the subrtx check 
> captures all operations and with the default settings (scalar-vec-cost = 0) 
> we 
> always prefer vv over vx/vf?

Yes, of course. The previous vx/vf combine patch(s) needs to do similar change 
too.
Let's wait for the CI and see.

Pan

-----Original Message-----
From: Robin Dapp <rdapp....@gmail.com> 
Sent: Wednesday, August 6, 2025 10:35 PM
To: Li, Pan2 <pan2...@intel.com>; gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; kito.ch...@gmail.com; jeffreya...@gmail.com; 
rdapp....@gmail.com; Chen, Ken <ken.c...@intel.com>; Liu, Hongtao 
<hongtao....@intel.com>
Subject: Re: [PATCH v1] RISC-V: Refactor the vec_duplicate cost on 
gpr/fpr2vr-cost param

Looks much more reasonable, thanks.

I assume the test expectation changes are necessary because the subrtx check 
captures all operations and with the default settings (scalar-vec-cost = 0) we 
always prefer vv over vx/vf?

-- 
Regards
 Robin

Reply via email to