On Dec 3, 2022, Richard Biener wrote:
>> On riscv64-elf and arm-eabi/-mcpu=cortex-r5, for example, though the
>> Warray-bounds-48.c condition passes, we don't issue warnings because
>> we decide not to vectorize the assignments.
> If it’s cost can you try-fno-vect-cost-model? If that works it m
> Am 03.12.2022 um 09:16 schrieb Alexandre Oliva via Gcc-patches
> :
>
>
> The bogus Wstringop-overflow warnings conditionally issued for
> Warray-bounds-48.c and -Wzero-length-array-bounds-2.c are expected
> under conditions that depend on the availability of certain vector
> patterns, but
The bogus Wstringop-overflow warnings conditionally issued for
Warray-bounds-48.c and -Wzero-length-array-bounds-2.c are expected
under conditions that depend on the availability of certain vector
patterns, but that don't take cost analysis into account, which
leads to omitted expected warnings a
