Assigning based on regression range.

Having a look

Okay, it looks like the way we inline the array constructor my initial constructor isn't respected...the initial constructor is chosen to have the map/elements-kind of the input array (which is fast elements), but instead we create a smi array.

The slow assert catches the mismatch.

There are a few options for the fix, will decide in the morning.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5

commit f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5
Author: Mike Stanton <mvstanton@chromium.org>
Date: Fri Oct 20 08:43:58 2017

Revert "[Turbofan] Array.prototype.filter inlining."

This reverts commit 9fd029ef25a0b4937d5298f4bdaecdb771842117.

Due to a ClusterFuzz issue.

TBR=mstarzinger@chromium.org

Bug:  chromium:776511 
Change-Id: I0f30e2e8de97f3c437a1756c82e645828358ad91
Reviewed-on: https://chromium-review.googlesource.com/730006
Reviewed-by: Michael Stanton <mvstanton@chromium.org>
Commit-Queue: Michael Stanton <mvstanton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48775}
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/builtins/builtins-array-gen.cc
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/builtins/builtins-definitions.h
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/builtins/builtins.cc
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/compiler/js-call-reducer.cc
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/compiler/js-call-reducer.h
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/src/deoptimizer.cc
[delete] https://crrev.com/14917b6531596d33590edb109ec14f6ca9b95536/test/mjsunit/optimized-filter.js
[modify] https://crrev.com/f0aa474e9adec4301c3a1c4f20f50db84e5dcbe5/test/mjsunit/regress/regress-crbug-747062.js
[delete] https://crrev.com/14917b6531596d33590edb109ec14f6ca9b95536/test/mjsunit/regress/regress-crbug-766635.js

ClusterFuzz has detected this issue as fixed in range 48774:48775.

Detailed report: https://clusterfuzz.com/testcase?key=4841831648198656

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  BackingStore::get(backing_store, i, isolate)->IsSmi() || (IsHoleyElementsKind(Ki
  ValidateContents
  ValidateImpl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48696:48697
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48774:48775

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4841831648198656

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4841831648198656 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot