| commit | 6ab674ebff5e60c62b126d0ac2e774e581916afe | |
| author | Mike Frysinger <vapier@gentoo.org> | |
| Mon, 19 Oct 2015 17:07:28 +0000 (19 13:07 -0400) | ||
| committer | Mike Frysinger <vapier@gentoo.org> | |
| Mon, 19 Oct 2015 19:36:48 +0000 (19 15:36 -0400) | ||
| tree | 72e72448b982e3715630f091e3be4612244f6589 | treesnapshot (tar.gz zip) |
| parent | cf6d542db3dfe26402b6adaa740a578b54767f65 | commitdiff |
use -fstack-protector-strong when available
With gcc-4.9, a new -fstack-protector-strong flag is available that is
between -fstack-protector (pretty weak) and -fstack-protector-all (pretty
strong) that provides good trade-offs between overhead but still providing
good coverage. Update the places in glibc that use ssp to use this flag
when it's available.
This also kills off the indirection of hardcoding the flag name in the
Makefiles and adding it based on a have-ssp boolean. Instead, the build
always expands the $(stack-protector) variable to the best ssp setting.
This makes the build logic a bit simpler and allows people to easily set
to a diff flag like:
make stack-protector=-fstack-protector-all
With gcc-4.9, a new -fstack-protector-strong flag is available that is
between -fstack-protector (pretty weak) and -fstack-protector-all (pretty
strong) that provides good trade-offs between overhead but still providing
good coverage. Update the places in glibc that use ssp to use this flag
when it's available.
This also kills off the indirection of hardcoding the flag name in the
Makefiles and adding it based on a have-ssp boolean. Instead, the build
always expands the $(stack-protector) variable to the best ssp setting.
This makes the build logic a bit simpler and allows people to easily set
to a diff flag like:
make stack-protector=-fstack-protector-all