[elements] Fix sorting dictionary element keys

[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
LOG=N

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

[Camillo Bruni, 2016-03-17 12:14:38]

Description was changed from

==========
[elements] Fix sorting dictionary element keys

BUG=chromium:594954
==========

to

==========
[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
==========

[Camillo Bruni, 2016-03-17 12:15:14]

cbruni@chromium.org changed reviewers:
+ verwaest@chromium.org

[Camillo Bruni, 2016-03-17 12:15:14]

PTAL

[Toon Verwaest, 2016-03-17 15:06:01]

Please specialize GetIterationLength to fast or slow elements kind to avoid
extra overhead for FastElements usages

[Camillo Bruni, 2016-03-17 19:42:42]

PTAL again

[Toon Verwaest, 2016-03-18 10:16:39]

awesome, thanks. LGTM

[Camillo Bruni, 2016-03-18 11:37:21]

The CQ bit was checked by cbruni@chromium.org

[commit-bot: I haz the power, 2016-03-18 11:37:31]

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

[commit-bot: I haz the power, 2016-03-18 11:43:04]

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

[commit-bot: I haz the power, 2016-03-18 11:43:04]

Try jobs failed on following builders:
  v8_presubmit on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/12578)

[Camillo Bruni, 2016-03-18 11:55:57]

Description was changed from

==========
[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
==========

to

==========
[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
LOG=N
==========

[Camillo Bruni, 2016-03-18 11:55:59]

The CQ bit was checked by cbruni@chromium.org

[commit-bot: I haz the power, 2016-03-18 11:56:11]

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

[commit-bot: I haz the power, 2016-03-18 12:42:58]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-18 12:44:22]

Description was changed from

==========
[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
LOG=N
==========

to

==========
[elements] Fix sorting dictionary element keys

Using std::sort on a FixedArray with HeapNumbers is not very GC friendly.
Adding a separate step to properly record possible HeapNumbers.

BUG=chromium:594954
LOG=N

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

[commit-bot: I haz the power, 2016-03-18 12:44:23]

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