I see. This failure comes from that we have zve32x (TARGET_VECTOR is true) in command line, and then we don't do the reinit in riscv_pragma_intrinsic in v1.
As I understand, we need something like below, no matter TARGET_VECTOR is true or false. Int flags_backup = flags; Int new_flags = flags | ...; reinit (); flags = flags_backup (); reinit (); > Also I guess all zvk* and zvbb may also need to be added as well, > but...I suspect it's not scalable way? If zvk* and zvbb doesn't introduce new modes, I suspect we don't need to add here, let me double check about it and update in v2. Pan -----Original Message----- From: Li, Pan2 <pan2...@intel.com> Sent: Thursday, March 28, 2024 3:32 PM To: Kito Cheng <kito.ch...@gmail.com> Cc: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; Wang, Yanzhang <yanzhang.w...@intel.com> Subject: RE: [PATCH v1] RISC-V: Allow RVV intrinsic for more function target Thanks kito, looks missed this part in test, let me check it out. Pan -----Original Message----- From: Kito Cheng <kito.ch...@gmail.com> Sent: Thursday, March 28, 2024 2:44 PM To: Li, Pan2 <pan2...@intel.com> Cc: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; Wang, Yanzhang <yanzhang.w...@intel.com> Subject: Re: [PATCH v1] RISC-V: Allow RVV intrinsic for more function target Just tried something interesting: $ riscv64-unknown-linux-gnu-gcc -march=rv64gc -O target_attribute_v_with_intrinsic-9.c -S # Work $ riscv64-unknown-linux-gnu-gcc -march=rv64gc_zve32x -O target_attribute_v_with_intrinsic-9.c -S # Not work Also I guess all zvk* and zvbb may also need to be added as well, but...I suspect it's not scalable way?
