https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
--- Comment #8 from Martin Sebor ---
I committed r244497 to avoid exercising the test case on that line on
non-x86_64 targets. It passes on x86_64 with the native compiler and with a
sparc-sun-solaris2.11 cross-compiler, in both ILP32 and LP64 m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
Rainer Orth changed:
What|Removed |Added
CC||ro at gcc dot gnu.org
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
Christophe Lyon changed:
What|Removed |Added
Target|poerpc64*-*-* |powerpc64*-*-*
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
--- Comment #5 from Martin Sebor ---
Author: msebor
Date: Thu Jan 12 18:50:26 2017
New Revision: 244382
URL: https://gcc.gnu.org/viewcvs?rev=244382&root=gcc&view=rev
Log:
PR testsuite/79051
gcc/testsuite/ChangeLog:
* gcc.dg/attr-alloc_s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
--- Comment #4 from Martin Sebor ---
Author: msebor
Date: Thu Jan 12 18:35:19 2017
New Revision: 244380
URL: https://gcc.gnu.org/viewcvs?rev=244380&root=gcc&view=rev
Log:
PR testsuite/791051 - FAIL: gcc.dg/attr-alloc_size-4.c (test for warnings,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
--- Comment #3 from Richard Biener ---
Btw, reassoc has code to do this but it runs too late (after VRP1). With all
early opts we have running it earlier might be an option (for GCC 8).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
--- Comment #2 from Richard Biener ---
I get
> ./cc1 -quiet t.c -O2 -Wall -Walloc-size-larger-than=1234 -fdump-tree-all-alias
t.c: In function ‘foo’:
t.c:18:3: warning: argument 1 range [1236, 2147483647] exceeds maximum object
size 1234 [-Wallo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79054
Martin Sebor changed:
What|Removed |Added
Target||poerpc64*-*-*
Host|
