| commit | 70c85915eace83142b84e4f65f5db421cf0c09e3 | |
| author | Mans Rullgard <mans@mansr.com> | |
| Sat, 15 Aug 2020 11:57:03 +0000 (15 12:57 +0100) | ||
| committer | Mans Rullgard <mans@mansr.com> | |
| Sat, 5 Sep 2020 15:19:25 +0000 (5 16:19 +0100) | ||
| tree | 1b9dc52094784f1030827ed6df1d309326807849 | treesnapshot (tar.gz zip) |
| parent | 8f6aaf97498ff7edc0dcb30192542b4d5924411c | commitdiff |
build: simplify stack protector setup
The old configure code was written before the stack protector was
widely available and stable. On modern systems, the compiler and
linker do the right thing if they support the flags at all.
Downgrade the protector from 'all' to 'strong' as the latter covers
any function taking the address of a stack object, providing good
protection with minimal overhead. Also enable it unconditionally
when available.
The old configure code was written before the stack protector was
widely available and stable. On modern systems, the compiler and
linker do the right thing if they support the flags at all.
Downgrade the protector from 'all' to 'strong' as the latter covers
any function taking the address of a stack object, providing good
protection with minimal overhead. Also enable it unconditionally
when available.
| configure.ac | diffblobblamehistory | |
| m4/gcc_stack_protect.m4 | [deleted file] | blobblamehistory |