1 files changed, 0 insertions, 49 deletions
diff --git a/src/3rdparty/v8/test/mjsunit/regress/regress-815.js b/src/3rdparty/v8/test/mjsunit/regress/regress-815.js
deleted file mode 100644
index 803c0fb..0000000
--- a/src/3rdparty/v8/test/mjsunit/regress/regress-815.js
+++ /dev/null
@@ -1,49 +0,0 @@
-// Copyright 2010 the V8 project authors. All rights reserved.
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions are
-// met:
-//
-//     * Redistributions of source code must retain the above copyright
-//       notice, this list of conditions and the following disclaimer.
-//     * Redistributions in binary form must reproduce the above
-//       copyright notice, this list of conditions and the following
-//       disclaimer in the documentation and/or other materials provided
-//       with the distribution.
-//     * Neither the name of Google Inc. nor the names of its
-//       contributors may be used to endorse or promote products derived
-//       from this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// 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.
-
-// 815 describes a situation in which the ARM code generator could
-// end up in a spilled scope in code that only worked in a register
-// allocated scope.  Test that this no longer happens.
-//
-// The code generated for unary + assumes that we are not in a spilled
-// scope.
-
-var o = new Object();
-
-// The code for the iterated-over object in for-in used to be emitted
-// in a spilled scope:
-for (x in +o) { }
-
-// Emitting code for the left hand side of a for-in.
-for (a[+o] in o) {}
-
-// The receiver in an obj[index](1, 2, 3) call:
-try {
-  o[+o](1,2,3)
-} catch(e) {
-  // It's OK as long as it does not hit an assert.
-}