tree ef6dd15dac52b24262deddf7535413a0c229d816
parent a23a97e3bf77bdd7fa01cd1f681d758a943db63a
author Daniel Micay <danielmicay@gmail.com> 1449268586 -0500
committer Daniel Micay <danielmicay@gmail.com> 1449298365 -0500

enable -fstack-protector-strong

This results in nearly all functions with the possibility of stack
corruption getting stack canaries, because it applies to any function
taking a reference to the frame or with a local array rather than just
the functions with arrays larger than 8 bytes. It was developed for use
in Chrome (and Chrome OS) and has also been adopted by various other
distributions (Arch, Fedora, Ubuntu, etc).

The code size increase ranges from ~1.5% to ~2.5%, compared to ~0.3% to
~0.7% with the more conservative switch. The increase in the performance
loss is usually minimal. The overall size increase once everything other
than C and C++ code is taken into account is minimal, and it greatly
improves the mitigation of stack buffer overflow vulnerabilities.

https://lwn.net/Articles/584225/

Change-Id: Ie83d381e09d94deb34c5ff142a101ba3d14cf3ba