Activate preserving of optimized code map accross GCs.

Activate preserving of optimized code map accross GCs.

This enables --noflush-optimized-code-cache which allows preserving
entries in the optimized code map accross GCs. This only applies to
values being reachable through other paths.

R=hpayer@chromium.org,hablich@chromium.org

Committed: https://crrev.com/1a8776db25b63c4ce718423772d1fd13f58eeab5
Cr-Commit-Position: refs/heads/master@{#29755}

[Michael Starzinger, 2015-07-03 09:58:45]

mstarzinger@chromium.org changed reviewers:
+ hablich@chromium.org, hpayer@chromium.org

[Michael Starzinger, 2015-07-03 09:58:45]

Michael: This has the chance to bust a Canary because of bad interaction with
the GC. We should time this CL so that it doesn't overlap with other risky
features being shipped (most likely after the branch point).
Hannes: PTAL.

[Hannes Payer (out of office), 2015-07-03 13:00:13]

lgtm

[Michael Hablich, 2015-07-03 13:22:24]

On 2015/07/03 13:00:13, Hannes Payer wrote:
> lgtm

Thanks for the heads-up. Let's ship this after branching. The current Canary is
to crashy ATM.

[Michael Hablich, 2015-07-16 12:54:24]

On 2015/07/03 at 13:22:24, Hablich wrote:
> On 2015/07/03 13:00:13, Hannes Payer wrote:
> > lgtm
> 
> Thanks for the heads-up. Let's ship this after branching. The current Canary
is to crashy ATM.

Heads-up: Going to submit this on Monday so it does not interfere with Dev.

[Michael Hablich, 2015-07-16 12:59:52]

On 2015/07/16 at 12:54:24, Hablich wrote:
> On 2015/07/03 at 13:22:24, Hablich wrote:
> > On 2015/07/03 13:00:13, Hannes Payer wrote:
> > > lgtm
> > 
> > Thanks for the heads-up. Let's ship this after branching. The current Canary
is to crashy ATM.
> 
> Heads-up: Going to submit this on Monday so it does not interfere with Dev.

To correct myself: next dev will be build from 45 so there should be no
interference

Nevertheless, I don't want to roll something unstable right during weekend. So
Sunday/Monday it is.

[Michael Hablich, 2015-07-20 13:53:28]

The CQ bit was checked by hablich@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-20 13:53:32]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1217863006/1

[Michael Hablich, 2015-07-20 13:54:52]

The CQ bit was unchecked by hablich@chromium.org

[Michael Hablich, 2015-07-20 13:54:59]

The CQ bit was checked by hablich@chromium.org

[commit-bot: I haz the power, 2015-07-20 13:55:03]

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

[commit-bot: I haz the power, 2015-07-20 14:18:48]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-07-20 14:19:03]

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

[Hannes Payer (out of office), 2015-07-28 07:27:47]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1255043003/ by hpayer@chromium.org.

The reason for reverting is: This CL may be the reason for the spike on memory
corruption. Tentatively reverting this CL.

BUG=chromium:512780
LOG=n.