PPC: [runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

PPC: [runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

Port aafc3e54848af981f02b076cc9cfe7e54a67ad6d

Original commit message:
    The FIRST-LAST_NONCALLABLE_SPEC_OBJECT_TYPE range was accidentially used
    in field type tracking, where we should check for JSReceiver instead
    (there's no need to exclude JSProxy or JSFunction from tracking).

    And the use in %_ClassOf was actually wrong and didn't match the C++
    implementation in JSReceiver::class_name() anymore. Now it's consistent
    again.

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

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

[MTBrandyberry, 2015-12-18 16:36:33]

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

[MTBrandyberry, 2015-12-18 16:36:35]

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

[MTBrandyberry, 2015-12-18 16:36:40]

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

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

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

[JoranSiu, 2015-12-18 17:40:37]

On 2015/12/18 16:36:49, mtbrandyberry wrote:

lgtm

[commit-bot: I haz the power, 2015-12-18 18:33:05]

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

[commit-bot: I haz the power, 2015-12-18 18:33:06]

Dry run: This issue passed the CQ dry run.

[MTBrandyberry, 2015-12-18 19:13:48]

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

[commit-bot: I haz the power, 2015-12-18 19:14:00]

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

[commit-bot: I haz the power, 2015-12-18 19:15:58]

Committed patchset #1 (id:1)

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

Description was changed from

==========
PPC: [runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

Port aafc3e54848af981f02b076cc9cfe7e54a67ad6d

Original commit message:
    The FIRST-LAST_NONCALLABLE_SPEC_OBJECT_TYPE range was accidentially used
    in field type tracking, where we should check for JSReceiver instead
    (there's no need to exclude JSProxy or JSFunction from tracking).

    And the use in %_ClassOf was actually wrong and didn't match the C++
    implementation in JSReceiver::class_name() anymore. Now it's consistent
    again.

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

to

==========
PPC: [runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

Port aafc3e54848af981f02b076cc9cfe7e54a67ad6d

Original commit message:
    The FIRST-LAST_NONCALLABLE_SPEC_OBJECT_TYPE range was accidentially used
    in field type tracking, where we should check for JSReceiver instead
    (there's no need to exclude JSProxy or JSFunction from tracking).

    And the use in %_ClassOf was actually wrong and didn't match the C++
    implementation in JSReceiver::class_name() anymore. Now it's consistent
    again.

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

Committed: https://crrev.com/5c33ac6ccd36c846d54aef2a44a6826804ea9a60
Cr-Commit-Position: refs/heads/master@{#32973}
==========

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

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