[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2020-04-22 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 Martin Sebor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2020-02-02 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P2

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2020-01-30 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|2019-05-07 00:00

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-09 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 --- Comment #5 from Marc Glisse --- Thanks. The unreduced file does not reproduce for me. But anyway, we warn for things like int a[1]; void f(int n){ for(int i=0;i

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-08 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 --- Comment #4 from Martin Liška --- Created attachment 46319 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46319&action=edit Unreduced test-case Yes, I used creduce. I'm attaching unreduced test-case.

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-07 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 --- Comment #3 from Marc Glisse --- (In reply to Andrew Pinski from comment #2) > Most likely used creduce to reduce the failure. creduce didn't use to produce such awful code. Part is because of -fpermissive, but part seems to be because the re

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-07 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 --- Comment #1 from Marc Glisse --- What kind of obfuscator did this go through?

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 --- Comment #2 from Andrew Pinski --- (In reply to Marc Glisse from comment #1) > What kind of obfuscator did this go through? Most likely used creduce to reduce the failure. NOTE sometimes creduce reduced are reduced into invalid/undefined cod

[Bug tree-optimization/90377] [10 Regression] New -Wstringop-overflow with -O3 since r270852

2019-05-07 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90377 Martin Liška changed: What|Removed |Added Last reconfirmed||2019-5-7 CC|