[Bug tree-optimization/110579] O2, O1 opmtimizations cause a buffer overflow panic during a strcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110579 --- Comment #5 from Gabriel --- I see. That makes sense. Our research project has a dataset with tar 1.14. Our plan is to compare our work with existing work in the dataset and to be consistent, use tar 1.14. We noticed our binary compiled with

[Bug tree-optimization/110579] O2, O1 opmtimizations cause a buffer overflow panic during a strcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110579 --- Comment #4 from Andrew Pinski --- All of these FORTIFY issues have been fixed for a long time now (over 10 years). Why are you trying to use an old version of gnu tar? e.g. https://lists.gnu.org/archive/html/bug-tar/2010-02/msg00010.html

[Bug tree-optimization/110579] O2, O1 opmtimizations cause a buffer overflow panic during a strcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110579 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug tree-optimization/110579] O2, O1 opmtimizations cause a buffer overflow panic during a strcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110579 --- Comment #2 from Sam James --- Could you give us a backtrace with -ggdb3 when it aborts at runtime?