[PATCH] Fix fallout from VRP strict-overflow changes
Andreas Schwab
schwab@linux-m68k.org
Fri Aug 18 23:52:00 GMT 2017
On Aug 17 2017, Richard Biener <rguenther@suse.de> wrote:
> I was notifed I broke proper handling of undefined overflow in
> multiplicative ops handling. The following resurrects previous
> behavior (and adds a testcase).
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
This breaks gfortran.dg/alloc_comp_auto_array_2.f90 on aarch64 with
-mabi=ilp32 (only for -O3):
FAIL: gfortran.dg/alloc_comp_auto_array_2.f90 -O3 -g (test for excess errors)
Excess errors:
/opt/gcc/gcc-20170818/gcc/testsuite/gfortran.dg/alloc_comp_auto_array_2.f90:33:0: Warning: '__builtin_memcpy' specified size between 2147483648 and 4294967295 exceeds maximum object size 2147483647 [-Wstringop-overflow=]
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Gcc-patches
mailing list