Remove SmartMove from array.js

test/mjsunit/bugs/bug-2615.js

Index: test/mjsunit/bugs/bug-2615.js
diff --git a/test/mjsunit/bugs/bug-2615.js b/test/mjsunit/bugs/bug-2615.js
index 51aeaf49244d858083d3975d9b39fe66789ff9f8..f9afa7930a97aa2f1ad39ce9e5abbe62cd87aa3b 100644
--- a/test/mjsunit/bugs/bug-2615.js
+++ b/test/mjsunit/bugs/bug-2615.js
@@ -24,7 +24,7 @@
 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
+/*

[rafaelw, 2014/06/22 23:59:19]

What's happening with this test is somewhat mysterious to me. For some reason,
when you run bleeding_edge check, this test doesn't fail -- unless I run it
directly.

However, it's clear the problem is performing array operations when the size is
very large (e.g. SimpleMove vs SmartMove) and the method gets pushed onto the JS
Path.

[Toon Verwaest, 2014/06/23 08:42:36]

I wrote this test at some point to have a list of all known JSArray bugs. Some
of these tests should now be fixed I presume (and some may run too slow as you
indicate). We should move the now working parts of this bug from bug to test.

On 2014/06/22 23:59:19, rafaelw wrote:

 var a = [];
 a[0xfffffffe] = 10;
 assertThrows("a.unshift(1);", RangeError);
@@ -124,3 +124,4 @@ assertThrows("a.sort();", TypeError);
 assertEquals([1,2,3,5,5,6], a);
 desc = Object.getOwnPropertyDescriptor(a, "4");
 assertEquals(false, desc.writable);
+*/