X87: Handle the case when derived constructor is [[Call]]ed with 0 args.

X87: Handle the case when derived constructor is [[Call]]ed with 0 args.

port cf53fed972896bf23c037ce7ac9f8e1512463c62 (r28242).

original commit message:

    ArgumentsAdaptorStub for derived constructor (the one that needs
    new.target) works in this way:
     - If the constructor is invoked via the Construct stub, we know that
       actual arguments always include new.target. ``arguments`` object
       however should not include a new.target, therefore we remove it.
       We achieve this by decrementing the argument count.
     - If the constructor is invoked as a call, we do not care for a correct
       ``arguments`` array since the constructor will immediately throw on
       entrance.
    The bug is that the call could actually pass 0 actual arguments, but I
    decrement unconditionally :(. The fix is to detect this case and avoid
    decrementing. ``arguments`` is bogus, but it is ok as constructor
    throws.

    Long-term we should just remove mucking about with arguments for
    new.target and just get it from the stack.

BUG=

Committed: https://crrev.com/5f047ff651a51a95f9625aab26c2a4a5f4f37587
Cr-Commit-Position: refs/heads/master@{#28246}

[chunyang.dai, 2015-05-06 02:29:43]

chunyang.dai@intel.com changed reviewers:
+ weiliang.lin@intel.com

[chunyang.dai, 2015-05-06 02:29:43]

PTAL.

[Weiliang, 2015-05-06 03:23:20]

The CQ bit was checked by weiliang.lin@intel.com

[Weiliang, 2015-05-06 03:23:21]

lgtm

[commit-bot: I haz the power, 2015-05-06 03:23:39]

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

[commit-bot: I haz the power, 2015-05-06 03:46:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-06 03:47:07]

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