[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2019-08-23 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 --- Comment #6 from Jeffrey A. Law --- *** Bug 81810 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2019-07-15 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 --- Comment #5 from Jeffrey A. Law --- Interestingly enough, it never comes up in gcc AFAICT, at least not the str* followed by memcpy/memset variant that shows up in that BZ. I don't think it'd be terribly hard to support, but if it's not

[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2019-07-15 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 --- Comment #4 from Martin Sebor --- I've seen code similar to it but I don't remember how close they were. I imagine it comes up quite a bit as GCC itself transforms code in various ways. DSE already eliminates stores with constant sizes but

[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2019-07-12 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2017-08-29 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/80576] dead strcpy and strncpy followed by memset not eliminated

2017-05-01 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80576 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill