Re: 回复: [PATCH] RISC-V/testsuite: Enable `vect_pack_trunc'

2023-10-10 Thread Maciej W. Rozycki 
On Mon, 9 Oct 2023, Maciej W. Rozycki wrote:

> > Btw, could you rebase to the trunk and run regression again?
> 
>  Full regression-testing takes roughly 40 hours here and I do not normally
> update the tree midway through my work so as not to add variables and end 
> up chasing a moving target, especially with such an unstable state that we 
> have ended up with recently with the RISC-V port.  Since I'm done with 
> this part I can refresh and schedule another run if you are curious as to 
> how it looks like from my side.  For the C subset alone it'll take less.

 After 10 hours I have now got:

=== gcc Summary ===

# of expected passes194576
# of unexpected failures600
# of unexpected successes   11
# of expected failures  1631
# of unresolved testcases   120
# of unsupported tests  3828

as at commit cc5033721553 ("Fixes for profile count/probability 
maintenance"), which is slightly better, but still far from your 92 FAILs.  
NB I ran this testing with `--param=riscv-autovec-preference=scalable'; I 
guess I could have mentioned it.

  Maciej

Re: 回复: [PATCH] RISC-V/testsuite: Enable `vect_pack_trunc'

2023-10-09 Thread Maciej W. Rozycki 
On Tue, 10 Oct 2023, 钟居哲 wrote:

> Btw, could you rebase to the trunk and run regression again?

 Full regression-testing takes roughly 40 hours here and I do not normally
update the tree midway through my work so as not to add variables and end 
up chasing a moving target, especially with such an unstable state that we 
have ended up with recently with the RISC-V port.  Since I'm done with 
this part I can refresh and schedule another run if you are curious as to 
how it looks like from my side.  For the C subset alone it'll take less.

  Maciej

回复: [PATCH] RISC-V/testsuite: Enable `vect_pack_trunc'

2023-10-09 Thread 钟居哲 
Btw, could you rebase to the trunk and run regression again?

I saw your report 670 FAILs:
# of expected passes   187616
# of unexpected failures   672
# of unexpected successes  14
# of expected failures 1436
# of unresolved testcases  615
# of unsupported tests 4731

I am recently working on fixing FAILs of risc-v regression. Your report looks 
odd.
This is my report:

# of expected passes183613
# of unexpected failures92
# of unexpected successes   12
# of expected failures  1383
# of unresolved testcases   4
# of unsupported tests  4223

This is my report. It should be less than 100 FAILs.


juzhe.zh...@rivai.ai
 
发件人： 钟居哲
发送时间： 2023-10-10 06:17
收件人： gcc-patches
抄送： macro; Jeff Law; rdapp.gcc; kito.cheng
主题： [PATCH] RISC-V/testsuite: Enable `vect_pack_trunc'
 && [check_effective_target_arm_little_endian])
 || ([istarget mips*-*-*]
 && [et-is-effective-target mips_msa])
+|| [istarget riscv*-*-*]
 || ([istarget s390*-*-*]
 && [check_effective_target_s390_vx])
  || [istarget amdgcn*-*-*] }}]

You should change it into:

|| ([istarget riscv*-*-*]
 && [check_effective_target_riscv_v])

Then, these additional FAILs will be removed:

with no changes (except for intermittent Python failures for C++) with the 
remaining testsuites.  There are a few of regressions in `-march=rv64gc' 
testing:
+FAIL: gcc.dg/vect/pr97678.c scan-tree-dump vect "vectorizing stmts using SLP"
+FAIL: gcc.dg/vect/slp-13-big-array.c scan-tree-dump-times vect "vectorizing 
stmts using SLP" 3
+FAIL: gcc.dg/vect/slp-13.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 3
+FAIL: gcc.dg/vect/pr97678.c -flto -ffat-lto-objects  scan-tree-dump vect 
"vectorizing stmts using SLP"
+FAIL: gcc.dg/vect/slp-13-big-array.c -flto -ffat-lto-objects  
scan-tree-dump-times vect "vectorizing stmts using SLP" 3
+FAIL: gcc.dg/vect/slp-13.c -flto -ffat-lto-objects  scan-tree-dump-times vect 
"vectorizing stmts using SLP" 3


juzhe.zh...@rivai.ai