[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2019-09-29 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 Martin Sebor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2018-03-07 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2018-03-07 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 Martin Sebor changed: What|Removed |Added Known to fail|7.0 |7.3.0, 8.0 --- Comment #10 from Martin Se

[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2017-01-02 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 --- Comment #9 from Martin Sebor --- Thanks for the reference. The strcmp(s, s) (and likewise memcmp(p, p, n)) case in bug 65452 is different because unlike this one, strcmp doesn't change the arrays pointed to by its arguments (which are also n

[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2017-01-02 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 --- Comment #8 from Marek Polacek --- For strcpy(s, s) see Bug 65452, which also contains a patch for -Wsame-arguments.

[Bug c/60256] No -Wuninitialized warning for strcpy copying to self

2016-12-23 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60256 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Status|UNCONFIRMED