[turbofan] Fix OSR-ed callee trigged ty do-expressions.

[turbofan] Fix OSR-ed callee trigged ty do-expressions.

This fixes a missing SSA-renaming of the callee value used in the frame
state of a call node. An OSR-entry within do-expressions contained in
one of the argument expression can trigger that renaming.

R=rossberg@chromium.org
TEST=mjsunit/regress/regress-crbug-546968
BUG=chromium:546968
LOG=n

Committed: https://crrev.com/f8465b45f7010adf3012d785bfc4ed217ad75404
Cr-Commit-Position: refs/heads/master@{#31613}

[rossberg, 2015-10-27 17:03:56]

Thanks! LGTM, although I can't claim I really understand why this fixes it. :)

[Michael Starzinger, 2015-10-27 17:18:40]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2015-10-27 17:18:52]

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

[caitp (gmail), 2015-10-27 17:19:04]

caitpotter88@gmail.com changed reviewers:
+ caitpotter88@gmail.com

[caitp (gmail), 2015-10-27 17:19:05]

https://codereview.chromium.org/1430483002/diff/1/src/compiler/ast-graph-buil...
File src/compiler/ast-graph-builder.cc (right):

https://codereview.chromium.org/1430483002/diff/1/src/compiler/ast-graph-buil...
src/compiler/ast-graph-builder.cc:1660: ast_context()->ReplaceValue();
Question: why does this matter? It looks like it just keeps the operand stack in
exactly the same state that it's already in

[commit-bot: I haz the power, 2015-10-27 17:21:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-27 17:21:20]

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