http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37130
Richard Guenther changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37130
Francois-Xavier Coudert changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
--- Comment #6 from scott dot gccbugs dot 2009 at scottrix dot co dot uk
2010-02-12 16:16 ---
I get this on 4.4.3 for x86 32bit, is there a patch, or will I have to wait for
4.5 to be released ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37130
--- Comment #5 from rguenth at gcc dot gnu dot org 2010-01-02 19:30 ---
Works with 4.4 and 4.5.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from enrio at online dot no 2009-10-23 10:06 ---
In my example code there is a pointer to a struct that has an array as the
first member. I appears that the compiler treats the pointer as a pointer to
this first member, and flags a loop that writes outside the first member
--- Comment #3 from enrio at online dot no 2009-10-23 07:41 ---
Created an attachment (id=18877)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18877&action=view)
Code that warns, 50 lines, no #include. #ifdef for variations w/o warning
--
http://gcc.gnu.org/bugzilla/show_bug.c
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-08-16 22:54 ---
__insertion_sort (&entry.node_id[0], &entry.node_id[16]);
The length is only 4.
One issue is that we don't reduce:
D.8167 = &entry.node_id[0] + (unsigned int) num_side_vert * 4;
if (&entry.node_id[0] != D.81
