Fix uninitialized new.target register in InvokeBuiltin.

Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n

Committed: https://crrev.com/77774035d85d9d7df2cb09a77bca45ce7c938482
Cr-Commit-Position: refs/heads/master@{#32622}

[Michael Starzinger, 2015-12-04 14:53:17]

Description was changed from

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=jarin@chromium.org
BUG=chromium:565046
LOG=n
==========

to

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n
==========

[Michael Starzinger, 2015-12-04 14:53:17]

mstarzinger@chromium.org changed reviewers:
+ ishell@chromium.org
- jarin@chromium.org

[Igor Sheludko, 2015-12-04 16:24:02]

lgtm

[Michael Starzinger, 2015-12-04 16:34:00]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2015-12-04 16:34:12]

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

[commit-bot: I haz the power, 2015-12-04 16:35:39]

Description was changed from

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n
==========

to

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n
==========

[commit-bot: I haz the power, 2015-12-04 16:35:40]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-12-04 16:35:56]

Description was changed from

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n
==========

to

==========
Fix uninitialized new.target register in InvokeBuiltin.

On some architectures the InvokeBuiltin sequence does not go through
InvokeFunctionCode, which initializes the new.target register. This
initializes the register explicitly on these architectures for now.

R=ishell@chromium.org
BUG=chromium:565046
LOG=n

Committed: https://crrev.com/77774035d85d9d7df2cb09a77bca45ce7c938482
Cr-Commit-Position: refs/heads/master@{#32622}
==========

[commit-bot: I haz the power, 2015-12-04 16:35:57]

Patchset 2 (id:??) landed as
https://crrev.com/77774035d85d9d7df2cb09a77bca45ce7c938482
Cr-Commit-Position: refs/heads/master@{#32622}