[json] Repair JSON.parse regression with non-sequential strings.

[json] Repair JSON.parse regression with non-sequential strings.

Make sure to flatten strings first in JSON.parse() builtins, otherwise
we always hit the slow path for non-sequential strings, i.e. for cons
strings.

Also don't create any arguments adaptor frames for JSON.parse() as the
C++ builtin can handle any number of inputs properly.

R=yangguo@chromium.org

Committed: https://crrev.com/e3c3be36eee9aa413fa309d5df88a2f18f24d2a1
Cr-Commit-Position: refs/heads/master@{#36722}

[Yang, 2016-06-03 18:22:00]

https://codereview.chromium.org/2039553002/diff/1/src/bootstrapper.cc
File src/bootstrapper.cc (right):

https://codereview.chromium.org/2039553002/diff/1/src/bootstrapper.cc#newcode...
src/bootstrapper.cc:1608: true);
do we need to change this for JSON.stringify too?

[Yang, 2016-06-03 18:22:09]

On 2016/06/03 18:22:00, Yang wrote:
> https://codereview.chromium.org/2039553002/diff/1/src/bootstrapper.cc
> File src/bootstrapper.cc (right):
> 
>
https://codereview.chromium.org/2039553002/diff/1/src/bootstrapper.cc#newcode...
> src/bootstrapper.cc:1608: true);
> do we need to change this for JSON.stringify too?

lgtm. thanks!

[Benedikt Meurer (Google), 2016-06-03 18:38:55]

The CQ bit was checked by bmeurer@google.com

[commit-bot: I haz the power, 2016-06-03 18:38:58]

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

[commit-bot: I haz the power, 2016-06-03 18:41:02]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-03 18:42:38]

Description was changed from

==========
[json] Repair JSON.parse regression with non-sequential strings.

Make sure to flatten strings first in JSON.parse() builtins, otherwise
we always hit the slow path for non-sequential strings, i.e. for cons
strings.

Also don't create any arguments adaptor frames for JSON.parse() as the
C++ builtin can handle any number of inputs properly.

R=yangguo@chromium.org
==========

to

==========
[json] Repair JSON.parse regression with non-sequential strings.

Make sure to flatten strings first in JSON.parse() builtins, otherwise
we always hit the slow path for non-sequential strings, i.e. for cons
strings.

Also don't create any arguments adaptor frames for JSON.parse() as the
C++ builtin can handle any number of inputs properly.

R=yangguo@chromium.org

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

[commit-bot: I haz the power, 2016-06-03 18:42:39]

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