[runtime] Migrate Object.create to C++.

[runtime] Migrate Object.create to C++.

There's no point in keeping the ObjectCreate JavaScript wrapper
function, which even does allocation site pretenuring for the
instances created via Object.create (where ObjectCreate itself is
the AllocationSite), and does not offer any sane way forward.

Instead introduce a new ObjectCreate C++ builtin, which currently
serves as a baseline implementation, on top of which we can think
about ways to optimize Object.create for the common case (i.e.
frameworks such as Ember.js make heavy use of Object.create).

R=cbruni@chromium.org
TBR=hpayer@chromium.org

Committed: https://crrev.com/6a51d31139500b8e4182bc8f0b3a942bdbc02d3e
Cr-Commit-Position: refs/heads/master@{#33061}

[Benedikt Meurer, 2015-12-29 18:47:17]

Hey Camillo,

Another easy one. As discussed before christmas, we want to make Object.create
better in the future. This provides a sane baseline w/o any weirdness in JS
builtins.
Please take a look.

Thanks,
Benedikt

TBRed heap owners for string addition in heap.h.

[Camillo Bruni, 2015-12-30 08:54:30]

LGTM with one nit (that you can ignore)

https://codereview.chromium.org/1558433002/diff/20001/src/builtins.cc
File src/builtins.cc (right):

https://codereview.chromium.org/1558433002/diff/20001/src/builtins.cc#newcode...
src/builtins.cc:1516: Handle<Object> properties = args.at<Object>(2);
you could use atOrUndefined here ;) (I have to sell my stuff, you know).

[Benedikt Meurer, 2015-12-30 13:13:46]

https://codereview.chromium.org/1558433002/diff/20001/src/builtins.cc
File src/builtins.cc (right):

https://codereview.chromium.org/1558433002/diff/20001/src/builtins.cc#newcode...
src/builtins.cc:1516: Handle<Object> properties = args.at<Object>(2);
Hah, gotcha :-)

[Benedikt Meurer, 2015-12-30 13:13:55]

The CQ bit was checked by bmeurer@chromium.org

[Benedikt Meurer, 2015-12-30 13:13:55]

The patchset sent to the CQ was uploaded after l-g-t-m from cbruni@chromium.org
Link to the patchset: https://codereview.chromium.org/1558433002/#ps40001
(title: "Address Camillos comment.")

[commit-bot: I haz the power, 2015-12-30 13:14:09]

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

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

Committed patchset #3 (id:40001)

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

Description was changed from

==========
[runtime] Migrate Object.create to C++.

There's no point in keeping the ObjectCreate JavaScript wrapper
function, which even does allocation site pretenuring for the
instances created via Object.create (where ObjectCreate itself is
the AllocationSite), and does not offer any sane way forward.

Instead introduce a new ObjectCreate C++ builtin, which currently
serves as a baseline implementation, on top of which we can think
about ways to optimize Object.create for the common case (i.e.
frameworks such as Ember.js make heavy use of Object.create).

R=cbruni@chromium.org
TBR=hpayer@chromium.org
==========

to

==========
[runtime] Migrate Object.create to C++.

There's no point in keeping the ObjectCreate JavaScript wrapper
function, which even does allocation site pretenuring for the
instances created via Object.create (where ObjectCreate itself is
the AllocationSite), and does not offer any sane way forward.

Instead introduce a new ObjectCreate C++ builtin, which currently
serves as a baseline implementation, on top of which we can think
about ways to optimize Object.create for the common case (i.e.
frameworks such as Ember.js make heavy use of Object.create).

R=cbruni@chromium.org
TBR=hpayer@chromium.org

Committed: https://crrev.com/6a51d31139500b8e4182bc8f0b3a942bdbc02d3e
Cr-Commit-Position: refs/heads/master@{#33061}
==========

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

Patchset 3 (id:??) landed as
https://crrev.com/6a51d31139500b8e4182bc8f0b3a942bdbc02d3e
Cr-Commit-Position: refs/heads/master@{#33061}