[Bug tree-optimization/59377] VRP produces bogus warning with -Warray-bounds

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59377

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|WAITING |RESOLVED

--- Comment #4 from Andrew Pinski  ---
The testcase provided in comment #0 is correctly warning about array bounds as
I had explained.  The testcase is reduced way too much from the original code
and there is no feedback in getting the original testcase in over 7 years so
just closing as invalid.

[Bug tree-optimization/59377] VRP produces bogus warning with -Warray-bounds

[ppluzhnikov at google dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59377

--- Comment #1 from Paul Pluzhnikov ppluzhnikov at google dot com ---
Google ref: b/7233326

[Bug tree-optimization/59377] VRP produces bogus warning with -Warray-bounds

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59377

Andrew Pinski pinskia at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
   Last reconfirmed||2013-12-03
 Ever confirmed|0   |1

--- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org ---
I think this is an invalid testcase.  GCC does not know what this strlen/memcmp
does.  If we add extern C around strlen and memcmp, GCC does not warn.

I think you over reduced the original testcase.

[Bug tree-optimization/59377] VRP produces bogus warning with -Warray-bounds

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59377

--- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #2)
 I think this is an invalid testcase.  GCC does not know what this
 strlen/memcmp does.  If we add extern C around strlen and memcmp, GCC does
 not warn.

Does not warn as GCC is able to optimize away the strlen (and even the memcmp
too).