From: Martin Vaeth <vaeth@mathematik.uni-wuerzburg.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Improve the security of the default profile
Date: Sat, 7 Sep 2013 19:52:07 +0000 (UTC) [thread overview]
Message-ID: <slrnl2n0vf.v04.vaeth@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: 1378579842.7654.11.camel@localhost
Pacho Ramos <pacho@gentoo.org> wrote:
>
> Is there any kind of information about performance penalty of
> -fstack-protector? I have googled some time and there are various
> estimations (from ~2 to ~8%), but I have no idea what have they checked
> exactly.
This depends extremely on the code: Most functions will be unchanged,
and only a few functions with possibly dangerous code get a fixed
impact whenever they are called. Whether they are called frequently
or not cannot be said in general.
> looks to me like it will have impact but "not too much" :/
Of course, it will have impact, but it is more theoretical than practical.
> For some recent computers I would probably use it,
> but for older ones, I am not sure if will be happy
> with that additional impact :|
On my old Pentium III laptop it makes no difference for my applications
which can be felt. Of course, if you have a special time-critical
application which just was on the limit, things might be different.
However,in such cases you would also use things like -DNDEBUG which one
would not choose as a default just because it gives some minimal
performance enhancement.
next prev parent reply other threads:[~2013-09-07 19:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 10:13 [gentoo-dev] Improve the security of the default profile Agostino Sarubbo
2013-09-05 10:47 ` Tom Wijsman
2013-09-05 10:54 ` Agostino Sarubbo
2013-09-05 11:09 ` Tom Wijsman
2013-09-05 11:58 ` Agostino Sarubbo
2013-09-05 13:33 ` Rich Freeman
2013-09-05 10:54 ` Sergey Popov
2013-09-05 11:06 ` [gentoo-dev] " Mike Frysinger
2013-09-07 3:48 ` Rick "Zero_Chaos" Farina
2013-09-07 6:36 ` Parker Schmitt
2013-09-05 12:09 ` [gentoo-dev] " Ciaran McCreesh
2013-09-05 12:38 ` Tom Wijsman
2013-09-07 18:24 ` [gentoo-dev] " Martin Vaeth
2013-09-07 17:25 ` Ryan Hill
2013-09-07 18:10 ` Martin Vaeth
[not found] ` < 20130907151110.13ebc8a2@caribou.gateway.2wire.net>
2013-09-07 18:37 ` Rich Freeman
2013-09-07 18:50 ` Pacho Ramos
2013-09-07 19:52 ` Martin Vaeth [this message]
2013-09-07 21:11 ` Ryan Hill
2013-09-07 23:08 ` Rick "Zero_Chaos" Farina
2013-09-07 23:12 ` Rich Freeman
2013-09-08 14:12 ` Hinnerk van Bruinehsen
2013-09-09 0:06 ` Ryan Hill
2013-09-09 12:11 ` Martin Vaeth
2013-09-09 12:21 ` Rich Freeman
2013-09-10 3:00 ` Ryan Hill
2013-09-10 3:46 ` Peter Stuge
2013-09-11 22:04 ` Magnus Granberg
2013-09-10 17:50 ` Jeroen Roovers
2013-09-10 22:41 ` Richard Yao
2013-09-11 1:17 ` Rich Freeman
2013-09-12 15:03 ` Richard Yao
2013-09-12 15:12 ` Richard Yao
2013-09-11 6:07 ` Ryan Hill
2013-09-11 18:23 ` Magnus Granberg
2013-09-12 15:07 ` Richard Yao
[not found] ` <522FA01E.4070602 @gentoo.org>
[not found] ` <CAGfcS_=VwAT0xYAny9hfd3tpRM61dt39Zcm7p0N8_pLzeyw1FQ@mail. gmail.com>
2013-09-11 4:49 ` Duncan
2013-09-11 6:49 ` Ryan Hill
2013-09-11 18:48 ` Magnus Granberg
2013-09-08 11:05 ` Martin Vaeth
2013-09-09 3:24 ` Ryan Hill
2013-09-08 11:24 ` Martin Vaeth
2013-09-12 15:23 ` Anthony G. Basile
2013-09-13 6:08 ` Ryan Hill
2013-09-07 19:50 ` Rick "Zero_Chaos" Farina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnl2n0vf.v04.vaeth@lounge.imp.fu-berlin.de \
--to=vaeth@mathematik.uni-wuerzburg.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox