RE: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization

2024-05-09 Thread Li, Pan2
Committed, thanks Juzhe. Pan From: juzhe.zh...@rivai.ai Sent: Thursday, May 9, 2024 5:05 PM To: Li, Pan2 ; gcc-patches Cc: kito.cheng ; Li, Pan2 Subject: Re: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization lgtm juzhe.zh...@rivai.ai

Re: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization

2024-05-09 Thread juzhe.zh...@rivai.ai
lgtm juzhe.zh...@rivai.ai From: pan2.li Date: 2024-05-09 11:05 To: gcc-patches CC: juzhe.zhong; kito.cheng; Pan Li Subject: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization From: Pan Li During investigate the support of early break autovec, we notice the test full-vec

[PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization

2024-05-08 Thread pan2 . li
From: Pan Li During investigate the support of early break autovec, we notice the test full-vec-move1.c will be optimized to 'return 0;' in main function body. Because somehow the value of V type is compiler time constant, and then the second loop will be considered as assert (true). Thus, th