diff options
author | Juzhe-Zhong <juzhe.zhong@rivai.ai> | 2023-10-10 20:55:47 +0800 |
---|---|---|
committer | Pan Li <pan2.li@intel.com> | 2023-10-10 21:28:29 +0800 |
commit | 8a361405375a82ed1975c72b9900a6775e0de037 (patch) | |
tree | f7ece3ce8e4d46fddaca68dd5996f54e3560406e /libgcc | |
parent | ddf17b6d71b87f7efe45b4b9ace6e12785b540ab (diff) | |
download | gcc-8a361405375a82ed1975c72b9900a6775e0de037.zip gcc-8a361405375a82ed1975c72b9900a6775e0de037.tar.gz gcc-8a361405375a82ed1975c72b9900a6775e0de037.tar.bz2 |
RISC-V Regression: Fix FAIL of pr65947-8.c for RVV
This test is testing fold_extract_last pattern so it's more reasonable use
vect_fold_extract_last instead of specifying targets.
This is the vect_fold_extract_last property:
proc check_effective_target_vect_fold_extract_last { } {
return [expr { [check_effective_target_aarch64_sve]
|| [istarget amdgcn*-*-*]
|| [check_effective_target_riscv_v] }]
}
include ARM SVE/GCN/RVV.
It perfectly matches what we want and more reasonable, better maintainment.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr65947-8.c: Use vect_fold_extract_last.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions