[runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

[runtime] Drop FIRST/LAST_NONCALLABLE_SPEC_OBJECT instance type range.

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=yangguo@chromium.org
BUG=chromium:535408
LOG=n

Committed: https://chromium.googlesource.com/v8/v8/+/aafc3e54848af981f02b076cc9cfe7e54a67ad6d

[Yang, 2015-12-17 05:49:21]

lgtm

[Benedikt Meurer, 2015-12-17 05:49:35]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-12-17 06:01:51]

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

[Benedikt Meurer, 2015-12-17 06:19:08]

The CQ bit was unchecked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-12-17 06:20:08]

Description was changed from

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

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=yangguo@chromium.org
BUG=chromium:535408
LOG=n
==========

to

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

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=yangguo@chromium.org
BUG=chromium:535408
LOG=n

Committed: https://crrev.com/aafc3e54848af981f02b076cc9cfe7e54a67ad6d
Cr-Commit-Position: refs/heads/master@{#32926}
==========

[commit-bot: I haz the power, 2015-12-17 06:20:09]

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

[Benedikt Meurer, 2015-12-17 06:20:10]

Description was changed from

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

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=yangguo@chromium.org
BUG=chromium:535408
LOG=n

Committed: https://crrev.com/aafc3e54848af981f02b076cc9cfe7e54a67ad6d
Cr-Commit-Position: refs/heads/master@{#32926}
==========

to

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

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=yangguo@chromium.org
BUG=chromium:535408
LOG=n

Committed:
https://chromium.googlesource.com/v8/v8/+/aafc3e54848af981f02b076cc9cfe7e54a6...
==========

[Benedikt Meurer, 2015-12-17 06:20:11]

Committed patchset #1 (id:1) manually as
aafc3e54848af981f02b076cc9cfe7e54a67ad6d (presubmit successful).