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

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

Reason for revert:
Official desktop continuous builder takes >8 hours while using up to 100% RAM and as much CPU it could get while still not hitting OOM.

Try 6 is scrubbed. The next attempt will be in late January 2016 or even February. We will try to reduce the requirements for RAM and CPU while linking the binaries with CFI.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome. Try 6.
>
> 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 sixth attempt to land the CL. Previous attempts:
> https://codereview.chromium.org/1502373003/
> https://codereview.chromium.org/1501593003/
> https://codereview.chromium.org/1393283005/
> https://codereview.chromium.org/1502233004/
> https://codereview.chromium.org/1513623004/
>
> The last time it failed, it was primarily due to the perf build slaves
> being much slower then the local build or other GCE slaves,
> see https://crbug.com/569732. This is still under investigation,
> and the timeout has been increased in the mean time:
> https://codereview.chromium.org/1528533003/
>
> Committed: https://crrev.com/14cb7878cb522ad05480547690ec3990f4bbb156
> Cr-Commit-Position: refs/heads/master@{#365486}

TBR=thestig@chromium.org,thakis@chromium.org,pcc@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
Committed: https://crrev.com/1e16347cc95833f00b9d7347cc35b12423ca6ddf
Cr-Commit-Position: refs/heads/master@{#365590}

[krasin, 2015-12-16 19:41:35]

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

[pcc1, 2015-12-16 19:42:12]

lgtm

[commit-bot: I haz the power, 2015-12-16 19:42:19]

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

[commit-bot: I haz the power, 2015-12-16 19:44:18]

Description was changed from

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

Reason for revert:
Official desktop continuous builder takes >8 hours while using up to 100% RAM
and as much CPU it could get while still not hitting OOM.

Try 6 is scrubbed. The next attempt will be in late January 2016 or even
February. We will try to reduce the requirements for RAM and CPU while linking
the binaries with CFI.


Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome. Try 6.
> 
> 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 sixth attempt to land the CL. Previous attempts:
> https://codereview.chromium.org/1502373003/
> https://codereview.chromium.org/1501593003/
> https://codereview.chromium.org/1393283005/
> https://codereview.chromium.org/1502233004/
> https://codereview.chromium.org/1513623004/
> 
> The last time it failed, it was primarily due to the perf build slaves
> being much slower then the local build or other GCE slaves,
> see https://crbug.com/569732. This is still under investigation,
> and the timeout has been increased in the mean time:
> https://codereview.chromium.org/1528533003/
> 
> Committed: https://crrev.com/14cb7878cb522ad05480547690ec3990f4bbb156
> Cr-Commit-Position: refs/heads/master@{#365486}

TBR=thestig@chromium.org,thakis@chromium.org,pcc@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

to

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

Reason for revert:
Official desktop continuous builder takes >8 hours while using up to 100% RAM
and as much CPU it could get while still not hitting OOM.

Try 6 is scrubbed. The next attempt will be in late January 2016 or even
February. We will try to reduce the requirements for RAM and CPU while linking
the binaries with CFI.


Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome. Try 6.
> 
> 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 sixth attempt to land the CL. Previous attempts:
> https://codereview.chromium.org/1502373003/
> https://codereview.chromium.org/1501593003/
> https://codereview.chromium.org/1393283005/
> https://codereview.chromium.org/1502233004/
> https://codereview.chromium.org/1513623004/
> 
> The last time it failed, it was primarily due to the perf build slaves
> being much slower then the local build or other GCE slaves,
> see https://crbug.com/569732. This is still under investigation,
> and the timeout has been increased in the mean time:
> https://codereview.chromium.org/1528533003/
> 
> Committed: https://crrev.com/14cb7878cb522ad05480547690ec3990f4bbb156
> Cr-Commit-Position: refs/heads/master@{#365486}

TBR=thestig@chromium.org,thakis@chromium.org,pcc@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

[commit-bot: I haz the power, 2015-12-16 19:44:19]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-16 19:45:12]

Description was changed from

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

Reason for revert:
Official desktop continuous builder takes >8 hours while using up to 100% RAM
and as much CPU it could get while still not hitting OOM.

Try 6 is scrubbed. The next attempt will be in late January 2016 or even
February. We will try to reduce the requirements for RAM and CPU while linking
the binaries with CFI.


Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome. Try 6.
> 
> 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 sixth attempt to land the CL. Previous attempts:
> https://codereview.chromium.org/1502373003/
> https://codereview.chromium.org/1501593003/
> https://codereview.chromium.org/1393283005/
> https://codereview.chromium.org/1502233004/
> https://codereview.chromium.org/1513623004/
> 
> The last time it failed, it was primarily due to the perf build slaves
> being much slower then the local build or other GCE slaves,
> see https://crbug.com/569732. This is still under investigation,
> and the timeout has been increased in the mean time:
> https://codereview.chromium.org/1528533003/
> 
> Committed: https://crrev.com/14cb7878cb522ad05480547690ec3990f4bbb156
> Cr-Commit-Position: refs/heads/master@{#365486}

TBR=thestig@chromium.org,thakis@chromium.org,pcc@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797
==========

to

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

Reason for revert:
Official desktop continuous builder takes >8 hours while using up to 100% RAM
and as much CPU it could get while still not hitting OOM.

Try 6 is scrubbed. The next attempt will be in late January 2016 or even
February. We will try to reduce the requirements for RAM and CPU while linking
the binaries with CFI.

Original issue's description:
> Enable Control Flow Integrity for the official Linux Chrome. Try 6.
>
> 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 sixth attempt to land the CL. Previous attempts:
> https://codereview.chromium.org/1502373003/
> https://codereview.chromium.org/1501593003/
> https://codereview.chromium.org/1393283005/
> https://codereview.chromium.org/1502233004/
> https://codereview.chromium.org/1513623004/
>
> The last time it failed, it was primarily due to the perf build slaves
> being much slower then the local build or other GCE slaves,
> see https://crbug.com/569732. This is still under investigation,
> and the timeout has been increased in the mean time:
> https://codereview.chromium.org/1528533003/
>
> Committed: https://crrev.com/14cb7878cb522ad05480547690ec3990f4bbb156
> Cr-Commit-Position: refs/heads/master@{#365486}

TBR=thestig@chromium.org,thakis@chromium.org,pcc@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:464797

Committed: https://crrev.com/1e16347cc95833f00b9d7347cc35b12423ca6ddf
Cr-Commit-Position: refs/heads/master@{#365590}
==========

[commit-bot: I haz the power, 2015-12-16 19:45:12]

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