Revert of Enable Control Flow Integrity for the official Linux Chrome.

Revert of Enable Control Flow Integrity for the official Linux Chrome. (patchset #1 id:1 of https://codereview.chromium.org/1501593003/ )

Reason for revert:
Buildbot timed out:
https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux%20x64/builds/6284

"command timed out: 3600 seconds without output, attempting to kill"

It's hard to say why does the buildbot so much slower than a local build. Possibly, not enough RAM.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome.
>
> This CL turns on CFI, a security check:
> https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-integrity
> http://clang.llvm.org/docs/ControlFlowIntegrity.html
>
> This feature enables LTO (Link-Time Optimization) builds, which slow down the linker by 3x-4x.
> CFI also comes with a code size overhead of about 7%-9%. The runtime CPU cost is less than 1%,
> and should not be an issue.
>
> BUG=chromium:464797
> Intent to Implement thread:
> https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pbJqt6ccMII/7iJC2oklCAAJ
>
> This is a second attempt to land the CL. The first one:
> https://codereview.chromium.org/1393283005/
>
> Committed: https://crrev.com/abbfcc7930834381e05c31068ac2256cb9ea4f49
> Cr-Commit-Position: refs/heads/master@{#363267}

TBR=thakis@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
Committed: https://crrev.com/931533d38f6b44a56f7a768e91d71f2f167c7897
Cr-Commit-Position: refs/heads/master@{#363313}

[krasin, 2015-12-05 00:01:20]

Created Revert of Enable Control Flow Integrity for the official Linux Chrome.

[commit-bot: I haz the power, 2015-12-05 00:04:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1501873002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1501873002/1

[commit-bot: I haz the power, 2015-12-05 00:04:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-12-05 00:04:07]

No L-G-T-M from a valid reviewer yet. Only full committers are accepted.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[pcc1, 2015-12-05 00:06:41]

lgtm

[krasin, 2015-12-05 00:08:01]

The CQ bit was checked by krasin@google.com

[krasin, 2015-12-05 00:08:09]

On 2015/12/05 00:06:41, pcc1 wrote:
> lgtm

Thank you, Peter!

[commit-bot: I haz the power, 2015-12-05 00:16:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1501873002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1501873002/1

[commit-bot: I haz the power, 2015-12-05 00:24:43]

Description was changed from

==========
Revert of Enable Control Flow Integrity for the official Linux Chrome. (patchset
#1 id:1 of https://codereview.chromium.org/1501593003/ )

Reason for revert:
Buildbot timed out:
https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux...

"command timed out: 3600 seconds without output, attempting to kill"

It's hard to say why does the buildbot so much slower than a local build.
Possibly, not enough RAM.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome.
> 
> This CL turns on CFI, a security check:
>
https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-i...
> http://clang.llvm.org/docs/ControlFlowIntegrity.html
> 
> This feature enables LTO (Link-Time Optimization) builds, which slow down the
linker by 3x-4x.
> CFI also comes with a code size overhead of about 7%-9%. The runtime CPU cost
is less than 1%,
> and should not be an issue.
> 
> BUG=chromium:464797
> Intent to Implement thread:
>
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pbJqt6ccMII/7iJC2...
> 
> This is a second attempt to land the CL. The first one:
> https://codereview.chromium.org/1393283005/
> 
> Committed: https://crrev.com/abbfcc7930834381e05c31068ac2256cb9ea4f49
> Cr-Commit-Position: refs/heads/master@{#363267}

TBR=thakis@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

to

==========
Revert of Enable Control Flow Integrity for the official Linux Chrome. (patchset
#1 id:1 of https://codereview.chromium.org/1501593003/ )

Reason for revert:
Buildbot timed out:
https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux...

"command timed out: 3600 seconds without output, attempting to kill"

It's hard to say why does the buildbot so much slower than a local build.
Possibly, not enough RAM.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome.
> 
> This CL turns on CFI, a security check:
>
https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-i...
> http://clang.llvm.org/docs/ControlFlowIntegrity.html
> 
> This feature enables LTO (Link-Time Optimization) builds, which slow down the
linker by 3x-4x.
> CFI also comes with a code size overhead of about 7%-9%. The runtime CPU cost
is less than 1%,
> and should not be an issue.
> 
> BUG=chromium:464797
> Intent to Implement thread:
>
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pbJqt6ccMII/7iJC2...
> 
> This is a second attempt to land the CL. The first one:
> https://codereview.chromium.org/1393283005/
> 
> Committed: https://crrev.com/abbfcc7930834381e05c31068ac2256cb9ea4f49
> Cr-Commit-Position: refs/heads/master@{#363267}

TBR=thakis@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

[commit-bot: I haz the power, 2015-12-05 00:24:44]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-05 00:26:11]

Description was changed from

==========
Revert of Enable Control Flow Integrity for the official Linux Chrome. (patchset
#1 id:1 of https://codereview.chromium.org/1501593003/ )

Reason for revert:
Buildbot timed out:
https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux...

"command timed out: 3600 seconds without output, attempting to kill"

It's hard to say why does the buildbot so much slower than a local build.
Possibly, not enough RAM.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome.
> 
> This CL turns on CFI, a security check:
>
https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-i...
> http://clang.llvm.org/docs/ControlFlowIntegrity.html
> 
> This feature enables LTO (Link-Time Optimization) builds, which slow down the
linker by 3x-4x.
> CFI also comes with a code size overhead of about 7%-9%. The runtime CPU cost
is less than 1%,
> and should not be an issue.
> 
> BUG=chromium:464797
> Intent to Implement thread:
>
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pbJqt6ccMII/7iJC2...
> 
> This is a second attempt to land the CL. The first one:
> https://codereview.chromium.org/1393283005/
> 
> Committed: https://crrev.com/abbfcc7930834381e05c31068ac2256cb9ea4f49
> Cr-Commit-Position: refs/heads/master@{#363267}

TBR=thakis@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

to

==========
Revert of Enable Control Flow Integrity for the official Linux Chrome. (patchset
#1 id:1 of https://codereview.chromium.org/1501593003/ )

Reason for revert:
Buildbot timed out:
https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux...

"command timed out: 3600 seconds without output, attempting to kill"

It's hard to say why does the buildbot so much slower than a local build.
Possibly, not enough RAM.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome.
>
> This CL turns on CFI, a security check:
>
https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-i...
> http://clang.llvm.org/docs/ControlFlowIntegrity.html
>
> This feature enables LTO (Link-Time Optimization) builds, which slow down the
linker by 3x-4x.
> CFI also comes with a code size overhead of about 7%-9%. The runtime CPU cost
is less than 1%,
> and should not be an issue.
>
> BUG=chromium:464797
> Intent to Implement thread:
>
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/pbJqt6ccMII/7iJC2...
>
> This is a second attempt to land the CL. The first one:
> https://codereview.chromium.org/1393283005/
>
> Committed: https://crrev.com/abbfcc7930834381e05c31068ac2256cb9ea4f49
> Cr-Commit-Position: refs/heads/master@{#363267}

TBR=thakis@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797

Committed: https://crrev.com/931533d38f6b44a56f7a768e91d71f2f167c7897
Cr-Commit-Position: refs/heads/master@{#363313}
==========

[commit-bot: I haz the power, 2015-12-05 00:26:12]

Patchset 1 (id:??) landed as
https://crrev.com/931533d38f6b44a56f7a768e91d71f2f167c7897
Cr-Commit-Position: refs/heads/master@{#363313}