[Bug middle-end/79123] incorrect -Walloca-larger-than: alloca may be too large due to conversion from long int to long unsigned int

2017-01-24 Thread aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79123 Aldy Hernandez changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/79123] incorrect -Walloca-larger-than: alloca may be too large due to conversion from long int to long unsigned int

2017-01-24 Thread aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79123 --- Comment #3 from Aldy Hernandez --- Author: aldyh Date: Tue Jan 24 09:50:33 2017 New Revision: 244859 URL: https://gcc.gnu.org/viewcvs?rev=244859=gcc=rev Log: PR middle-end/79123 * gimple-ssa-warn-alloca.c (alloca_call_type):

[Bug middle-end/79123] incorrect -Walloca-larger-than: alloca may be too large due to conversion from long int to long unsigned int

2017-01-18 Thread aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79123 --- Comment #2 from Aldy Hernandez --- [Just thinking out loud here.] Yeah. There's no correct range information available. For the argument to alloca we have: # RANGE ~[2305843009213693952, 16140901064495857663] n_9 = (long unsigned

[Bug middle-end/79123] incorrect -Walloca-larger-than: alloca may be too large due to conversion from long int to long unsigned int

2017-01-18 Thread aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79123 Aldy Hernandez changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|