[crankshaft] Do not optimize argument access if any parameter is context-allocated.

[crankshaft] Do not optimize argument access if any parameter is context-allocated.

Note: This CL might regress code that relies on such arguments access.
In that case, we could still optimize the access if it accesses at
constant index (and the argument at that index is not context-allocated).

If any code relies on a general access to context-allocated arguments,
we would need to analyze the function for assignment to the arguments - this
might be quite tricky.

BUG=chromium:662845
Committed: https://crrev.com/7f801ff35bfd8eac6fc0e64a1b12471ba90f7ad8
Cr-Commit-Position: refs/heads/master@{#40813}

[Jarin, 2016-11-07 15:07:09]

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

[commit-bot: I haz the power, 2016-11-07 15:07:20]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-07 15:31:15]

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

[commit-bot: I haz the power, 2016-11-07 15:31:16]

Dry run: This issue passed the CQ dry run.

[Jarin, 2016-11-07 15:55:21]

jarin@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Jarin, 2016-11-07 15:55:22]

Could you take a look, please?

[Benedikt Meurer, 2016-11-07 18:34:57]

lgtm

[Jarin, 2016-11-07 19:06:43]

The CQ bit was checked by jarin@chromium.org

[commit-bot: I haz the power, 2016-11-07 19:06:47]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-07 19:09:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-17 22:25:08]

Description was changed from

==========
[crankshaft] Do not optimize argument access if any parameter is
context-allocated.

Note: This CL might regress code that relies on such arguments access.
In that case, we could still optimize the access if it accesses at
constant index (and the argument at that index is not context-allocated).

If any code relies on a general access to context-allocated arguments,
we would need to analyze the function for assignment to the arguments - this
might be quite tricky.

BUG=chromium:662845
==========

to

==========
[crankshaft] Do not optimize argument access if any parameter is
context-allocated.

Note: This CL might regress code that relies on such arguments access.
In that case, we could still optimize the access if it accesses at
constant index (and the argument at that index is not context-allocated).

If any code relies on a general access to context-allocated arguments,
we would need to analyze the function for assignment to the arguments - this
might be quite tricky.

BUG=chromium:662845

Committed: https://crrev.com/7f801ff35bfd8eac6fc0e64a1b12471ba90f7ad8
Cr-Commit-Position: refs/heads/master@{#40813}
==========

[commit-bot: I haz the power, 2016-11-17 22:25:09]

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