https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
--- Comment #9 from Aldy Hernandez ---
Author: aldyh
Date: Wed Sep 13 17:28:29 2017
New Revision: 252570
URL: https://gcc.gnu.org/viewcvs?rev=252570=gcc=rev
Log:
PR middle-end/81908 - FAIL: gfortran.dg/alloc_comp_auto_array_2.f90 -O3 -g -m32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
--- Comment #7 from Martin Sebor ---
Author: msebor
Date: Fri Aug 25 00:25:57 2017
New Revision: 251347
URL: https://gcc.gnu.org/viewcvs?rev=251347=gcc=rev
Log:
PR middle-end/81908 - FAIL: gfortran.dg/alloc_comp_auto_array_2.f90 -O3 -g -m32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
Christophe Lyon changed:
What|Removed |Added
Target|i?86-*-*|i?86-*-*
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
--- Comment #4 from Martin Sebor ---
Below is a small test case that attempts to illustrate the point from comment
#3 about the same logic as for -Walloc-size-larger-than perhaps not applying
quite as well to -Wstringop-overflow.
The odds are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
--- Comment #3 from Martin Sebor ---
(In reply to Richard Biener from comment #1)
The code was originally designed for -Walloc-size-larger-than and does the
right thing for that warning. The range I see is
_248: ~[1, 2147483647]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
--- Comment #2 from Richard Biener ---
Btw, the anti-ranges can be made "signed" by
/* If we have an unsigned anti-range convert it to the respective
signed type. */
if (range_type == VR_ANTI_RANGE
&& TYPE_UNSIGNED (exptype)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81908
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
