https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065
--- Comment #27 from Alexander Cherepanov <ch3root at openwall dot com> --- On 2015-11-11 11:16, ebotcazou at gcc dot gnu.org wrote: > On 2015-11-11 03:36, danielmicay at gmail dot com wrote: >> The implementation of -fstack-check in GCC does have significant overhead, >> but it doesn't have to be that way. It shouldn't go out of the way to >> provide a proper stack trace with -O2/-O3 (or whatever other reasons it has >> for the slow implementation). > > Figures please, otherwise that's just FUD as usual. Are you saying that -fstack-check is ready for use? Why it's not documented (except for Ada and in gccint)? According to comments[1][2] by Florian Wiemer (cc'd) in 2013 it's not production-ready and "used to be rather buggy". Is this changed? [1] https://gcc.gnu.org/ml/gcc-patches/2013-09/msg01176.html [2] http://www.openwall.com/lists/oss-security/2013/01/23/4
