PPC: [builtins] Make Math.max and Math.min fast by default.

PPC: [builtins] Make Math.max and Math.min fast by default.

Port cb9b801069c432e745f0651cf00d65ef88cd7f06

Original commit message:
    The previous versions of Math.max and Math.min made it difficult to
    optimize those (that's why we already have custom code in Crankshaft),
    and due to lack of ideas what to do about the variable number of
    arguments, we will probably need to stick in special code in TurboFan
    as well; so inlining those builtins is off the table, hence there's no
    real advantage in having them around as "not quite JS" with extra work
    necessary in the optimizing compilers to still make those builtins
    somewhat fast in cases where we cannot inline them (also there's a
    tricky deopt loop in Crankshaft related to Math.min and Math.max, but
    that will be dealt with later).

    So to sum up: Instead of trying to make Math.max and Math.min semi-fast
    in the optimizing compilers with weird work-arounds support %_Arguments
    %_ArgumentsLength, we do provide the optimal code as native builtins
    instead and call it a day (which gives a nice performance boost on some
    benchmarks).

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=

Committed: https://crrev.com/3641a448836c08b691650eeddade07a5ee417031
Cr-Commit-Position: refs/heads/master@{#33618}

[MTBrandyberry, 2016-01-29 16:21:29]

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

[commit-bot: I haz the power, 2016-01-29 16:21:35]

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

[commit-bot: I haz the power, 2016-01-29 16:43:07]

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

[commit-bot: I haz the power, 2016-01-29 16:43:08]

Dry run: This issue passed the CQ dry run.

[michael_dawson, 2016-01-29 18:13:59]

On 2016/01/29 16:43:08, commit-bot: I haz the power wrote:
> Dry run: This issue passed the CQ dry run.

lgtm

[MTBrandyberry, 2016-01-29 19:29:27]

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

[commit-bot: I haz the power, 2016-01-29 19:29:38]

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

[commit-bot: I haz the power, 2016-01-29 19:32:44]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-29 19:33:13]

Description was changed from

==========
PPC: [builtins] Make Math.max and Math.min fast by default.

Port cb9b801069c432e745f0651cf00d65ef88cd7f06

Original commit message:
    The previous versions of Math.max and Math.min made it difficult to
    optimize those (that's why we already have custom code in Crankshaft),
    and due to lack of ideas what to do about the variable number of
    arguments, we will probably need to stick in special code in TurboFan
    as well; so inlining those builtins is off the table, hence there's no
    real advantage in having them around as "not quite JS" with extra work
    necessary in the optimizing compilers to still make those builtins
    somewhat fast in cases where we cannot inline them (also there's a
    tricky deopt loop in Crankshaft related to Math.min and Math.max, but
    that will be dealt with later).

    So to sum up: Instead of trying to make Math.max and Math.min semi-fast
    in the optimizing compilers with weird work-arounds support %_Arguments
    %_ArgumentsLength, we do provide the optimal code as native builtins
    instead and call it a day (which gives a nice performance boost on some
    benchmarks).

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
==========

to

==========
PPC: [builtins] Make Math.max and Math.min fast by default.

Port cb9b801069c432e745f0651cf00d65ef88cd7f06

Original commit message:
    The previous versions of Math.max and Math.min made it difficult to
    optimize those (that's why we already have custom code in Crankshaft),
    and due to lack of ideas what to do about the variable number of
    arguments, we will probably need to stick in special code in TurboFan
    as well; so inlining those builtins is off the table, hence there's no
    real advantage in having them around as "not quite JS" with extra work
    necessary in the optimizing compilers to still make those builtins
    somewhat fast in cases where we cannot inline them (also there's a
    tricky deopt loop in Crankshaft related to Math.min and Math.max, but
    that will be dealt with later).

    So to sum up: Instead of trying to make Math.max and Math.min semi-fast
    in the optimizing compilers with weird work-arounds support %_Arguments
    %_ArgumentsLength, we do provide the optimal code as native builtins
    instead and call it a day (which gives a nice performance boost on some
    benchmarks).

R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=

Committed: https://crrev.com/3641a448836c08b691650eeddade07a5ee417031
Cr-Commit-Position: refs/heads/master@{#33618}
==========

[commit-bot: I haz the power, 2016-01-29 19:33:14]

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