[Bug other/112897] Have a configure option for all common flags used by default on distros

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112897 --- Comment #2 from Agostino Sarubbo --- I don't know if I was able to provide the concept, but in other words if we know that something like -fstack-clash-protection is widely used nowadays, it make no sense rebase patches for 10 years and

[Bug other/112897] New: Have a configure option for all common flags used by default on distros

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112897 Bug ID: 112897 Summary: Have a configure option for all common flags used by default on distros Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity:

[Bug tree-optimization/112635] stack smash protection does not work when code is compiled with -O

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112635 Agostino Sarubbo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/112635] stack smash protection does not work when code is compiled with -O

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112635 --- Comment #2 from Agostino Sarubbo --- (In reply to Richard Biener from comment #1) > Yep, GCC fixes the code for you by eliding 'buf'. That's perfectly OK though > since the code invokes undefined behavior. > > I'm inclined to close this

[Bug libgcc/112635] New: stack smash protection does not work when code is compiled with -O

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112635 Bug ID: 112635 Summary: stack smash protection does not work when code is compiled with -O Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug other/112589] New: man gcc does not specify the default behavior of -fcf-protection when used without arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112589 Bug ID: 112589 Summary: man gcc does not specify the default behavior of -fcf-protection when used without arguments Product: gcc Version: 13.2.1 Status: UNCONFIRMED