1 |
On Sat, Sep 7, 2013 at 2:10 PM, Martin Vaeth |
2 |
<vaeth@××××××××××××××××××××××××.de> wrote: |
3 |
> Ryan Hill <dirtyepic@g.o> wrote: |
4 |
>> |
5 |
>> * -fstack-protector{-all} |
6 |
>> No thank you. -fstack-protector has very limited coverage |
7 |
> |
8 |
> I'd say it covers most cases where bugs can be made, |
9 |
> practically without a severe impact on execution time or code size. |
10 |
> In contrast, -fstack-protector-all should be left to hardened, since |
11 |
> its impact is unacceptable to e.g. multimedia systems - the |
12 |
> protection is probably over-the-top for normal users. |
13 |
> I'd vote for enabling -fstack-protector by default: |
14 |
> I am using it since many years (though I do not use hardened profile, |
15 |
> since -fstack-protector-all had too much a performance impact for me). |
16 |
> |
17 |
>> -fstack-protector-strong |
18 |
> |
19 |
> One can later still change to this when >=gcc-4.9 is available in stable. |
20 |
|
21 |
++, ++ |
22 |
|
23 |
No doubt stack-protector-strong is better than stack-protector, but |
24 |
stack-protector is still better than nothing, and nothing is the |
25 |
current default. |
26 |
|
27 |
Improvements don't need to be perfect - they just need to be improvements. |
28 |
|
29 |
Rich |