PPC: [runtime] Introduce dedicated JSBoundFunction to represent bound functions.

PPC: [runtime] Introduce dedicated JSBoundFunction to represent bound functions.

Port 97def8070cbb979419c041c3732d5e11779f79da

Original commit message:
    According to the ES2015 specification, bound functions are exotic
    objects, and thus don't need to be implemented as JSFunctions. So
    we introduce a new JSBoundFunction type to represent bound functions
    and make them optimizable. This already improves the performance of
    calling or constructing bound functions by 10-100x depending on the
    use case because we avoid the crazy dance between JavaScript and C++
    that was implemented in v8natives.js previously.

    There's still room for improvement in the performance of actually
    creating bound functions, which is also relevant in practice, but
    we already have a plan how to accomplish that later.

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=chromium:535408, chromium:571299, v8:4629
LOG=n

Committed: https://crrev.com/974e50ba0d2150d8f8f74a88c03cea6e67897095
Cr-Commit-Position: refs/heads/master@{#33064}

[MTBrandyberry, 2015-12-30 14:41:44]

The CQ bit was checked by mbrandy@us.ibm.com to run a CQ dry run

[commit-bot: I haz the power, 2015-12-30 14:41:46]

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

[JoranSiu, 2015-12-30 16:00:34]

On 2015/12/30 14:48:27, mtbrandyberry wrote:

lgtm

[JoranSiu, 2015-12-30 16:00:39]

On 2015/12/30 14:48:27, mtbrandyberry wrote:

lgtm

[MTBrandyberry, 2015-12-30 16:15:50]

The CQ bit was unchecked by mbrandy@us.ibm.com

[MTBrandyberry, 2015-12-30 16:16:14]

The CQ bit was checked by mbrandy@us.ibm.com

[commit-bot: I haz the power, 2015-12-30 16:16:18]

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

[commit-bot: I haz the power, 2015-12-30 16:41:55]

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

[commit-bot: I haz the power, 2015-12-30 16:41:56]

Try jobs failed on following builders:
  v8_linux_gcc_compile_rel on tryserver.v8 (JOB_TIMED_OUT, no build URL)

[MTBrandyberry, 2015-12-30 16:42:48]

The CQ bit was checked by mbrandy@us.ibm.com

[commit-bot: I haz the power, 2015-12-30 16:42:56]

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

[commit-bot: I haz the power, 2015-12-30 16:44:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-30 16:45:30]

Description was changed from

==========
PPC: [runtime] Introduce dedicated JSBoundFunction to represent bound functions.

Port 97def8070cbb979419c041c3732d5e11779f79da

Original commit message:
    According to the ES2015 specification, bound functions are exotic
    objects, and thus don't need to be implemented as JSFunctions. So
    we introduce a new JSBoundFunction type to represent bound functions
    and make them optimizable. This already improves the performance of
    calling or constructing bound functions by 10-100x depending on the
    use case because we avoid the crazy dance between JavaScript and C++
    that was implemented in v8natives.js previously.

    There's still room for improvement in the performance of actually
    creating bound functions, which is also relevant in practice, but
    we already have a plan how to accomplish that later.

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=chromium:535408, chromium:571299, v8:4629
LOG=n
==========

to

==========
PPC: [runtime] Introduce dedicated JSBoundFunction to represent bound functions.

Port 97def8070cbb979419c041c3732d5e11779f79da

Original commit message:
    According to the ES2015 specification, bound functions are exotic
    objects, and thus don't need to be implemented as JSFunctions. So
    we introduce a new JSBoundFunction type to represent bound functions
    and make them optimizable. This already improves the performance of
    calling or constructing bound functions by 10-100x depending on the
    use case because we avoid the crazy dance between JavaScript and C++
    that was implemented in v8natives.js previously.

    There's still room for improvement in the performance of actually
    creating bound functions, which is also relevant in practice, but
    we already have a plan how to accomplish that later.

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=chromium:535408, chromium:571299, v8:4629
LOG=n

Committed: https://crrev.com/974e50ba0d2150d8f8f74a88c03cea6e67897095
Cr-Commit-Position: refs/heads/master@{#33064}
==========

[commit-bot: I haz the power, 2015-12-30 16:45:30]

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