Re: [PATCH] vect: Ensure both NITERSM1 and NITERS are INTEGER_CSTs or neither of them [PR113210]

On Tue, 9 Jan 2024, Jakub Jelinek wrote: > Hi! > > On the following testcase e.g. on riscv64 or aarch64 (latter with > -O3 -march=armv8-a+sve ) we ICE, because while NITERS is INTEGER_CST, > NITERSM1 is a complex expression like > (short unsigned int) (a.0_1 + 255) + 1 > 256 ? ~(short unsigned

[PATCH] vect: Ensure both NITERSM1 and NITERS are INTEGER_CSTs or neither of them [PR113210]

Hi! On the following testcase e.g. on riscv64 or aarch64 (latter with -O3 -march=armv8-a+sve ) we ICE, because while NITERS is INTEGER_CST, NITERSM1 is a complex expression like (short unsigned int) (a.0_1 + 255) + 1 > 256 ? ~(short unsigned int) (a.0_1 + 255) : 0 where a.0_1 is unsigned char.