Restore -pie linker flag on Linux.

Restore -pie linker flag on Linux.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=124072

[Chris Evans, 2012-02-28 21:58:44]

I think this is the simplest way to restore things. Note that this CL enables
for all Linux platforms. This includes ARM which may not have been included
previously. I think it's important to try; we can back off to just ia32 and x64
if necessary.

[Elliot Glaysher, 2012-02-28 22:03:02]

lgtm

[Nico, 2012-02-29 02:47:45]

This increases binary size by 5MB (!):
http://build.chromium.org/f/chromium/perf/linux-release-64/sizes/report.html?...

[cevans, 2012-02-29 02:50:29]

Yeah, sorry. We've previously decided to take this hit, though. This change
is effectively just reverting a  recent security regression.

On Tue, Feb 28, 2012 at 6:47 PM, <thakis@chromium.org> wrote:

> This increases binary size by 5MB (!):
> http://build.chromium.org/f/**chromium/perf/linux-release-**
>
64/sizes/report.html?history=**150&rev=-1<http://build.chromium.org/f/chromium/perf/linux-release-64/sizes/report.html?history=150&rev=-1>
>
>
https://chromiumcodereview.**appspot.com/9514014/<https://chromiumcodereview....
>

[Nico, 2012-02-29 02:57:51]

On Tue, Feb 28, 2012 at 6:50 PM, Chris Evans <cevans@google.com> wrote:
> Yeah, sorry. We've previously decided to take this hit, though. This change
> is effectively just reverting a  recent security regression.

Did you measure how much start up time a > 5% binary size increase costs?

[cevans, 2012-02-29 03:02:31]

On Tue, Feb 28, 2012 at 6:57 PM, Nico Weber <thakis@chromium.org> wrote:

> On Tue, Feb 28, 2012 at 6:50 PM, Chris Evans <cevans@google.com> wrote:
> > Yeah, sorry. We've previously decided to take this hit, though. This
> change
> > is effectively just reverting a  recent security regression.
>
> Did you measure how much start up time a > 5% binary size increase costs?
>

I don't think we did (this was back in Jun 2011), the sordid history is
https://code.google.com/p/chromium/issues/detail?id=57908 on which I've
just cc:ed you. Note that we've been running with that hit, whatever is it,
on stable channel for multiple releases now. The thing I just fixed is
restoring back to our current stable behaviour -- the regression is a
recent thing on trunk.\