Periodic merge of bleeding_edge to experimental code generator branch....

test/mozilla/mozilla.status

 # Copyright 2008 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
@@ skipping 199 matching lines @@
 
 #:=== RegExp:=== 
 # To be compatible with KJS we silently ignore flags that do not make
 # sense.  This test expects us to throw exceptions.  
 ecma_3/RegExp/regress-57631: FAIL_OK
 
 # PCRE doesn't allow subpattern nesting deeper than 200, this tests
 # depth 500.  KJS detects the case, and return null from the match,
 # and passes this test (the test doesn't check for a correct return
 # value).
-ecma_3/RegExp/regress-119909: FAIL_OK
+ecma_3/RegExp/regress-119909: PASS || FAIL_OK
 
 
 # Difference in the way capturing subpatterns work.  In JS, when the
 # 'minimum repeat count' is reached, the empty string must not match.
 # In this case, we are similar but not identical to KJS.  Hard to
 # support the JS behavior with PCRE, so maybe emulate KJS?
 #
 # Note: We do not support toSource currently so we cannot run this
 # test. We should make an isolated test case for the regexp issue.
 ecma_3/RegExp/regress-209919: FAIL_OK
 
 
 # PCRE's match limit is reached.  SpiderMonkey hangs on the first one,
 # KJS returns true somehow.  Maybe they up the match limit?  There is
 # an open V8 bug 676063 about this.
 ecma_3/RegExp/regress-330684: FAIL_OK
 
 
+# This test contains a regexp that runs exponentially long.  Spidermonkey
+# standalone will hang, though apparently inside Firefox it will trigger a
+# long-running-script timeout.  JSCRE passes by hitting the matchLimit and
+# just pretending that an exhaustive search found no match.
+ecma_3/RegExp/regress-307456: PASS || FAIL_OK
+
+
 # We do not detect overflow in bounds for back references and {}
 # quantifiers.  Might fix by parsing numbers differently?
 js1_5/Regress/regress-230216-2: FAIL_OK
 
 
 # According to ECMA-262, \b is a 'word' boundary, where words are only
 # ASCII characters.  PCRE supports non-ASCII word characters.
 js1_5/Regress/regress-247179: FAIL_OK
 
 
 # Regexp too long for PCRE.
-js1_5/Regress/regress-280769: FAIL_OK
-js1_5/Regress/regress-280769-1: FAIL_OK
-js1_5/Regress/regress-280769-2: FAIL_OK
-js1_5/Regress/regress-280769-4: FAIL_OK
-js1_5/Regress/regress-280769-5: FAIL_OK
+js1_5/Regress/regress-280769: PASS || FAIL
+js1_5/Regress/regress-280769-1: PASS || FAIL
+js1_5/Regress/regress-280769-2: PASS || FAIL
+js1_5/Regress/regress-280769-4: PASS || FAIL
+js1_5/Regress/regress-280769-5: PASS || FAIL
 
 
 # We do not support static RegExp.multiline - should we?.
 js1_2/regexp/RegExp_multiline: FAIL_OK
 js1_2/regexp/RegExp_multiline_as_array: FAIL_OK
 js1_2/regexp/beginLine: FAIL_OK
 js1_2/regexp/endLine: FAIL_OK
 
 
 # Date trouble?
@@ skipping 14 matching lines @@
 
 
 # Stack overflows should be InternalError: too much recursion?
 js1_5/Regress/regress-234389: FAIL_OK
 
 
 # This may very well be a bogus test. I'm not sure yet.
 js1_5/Regress/regress-320119: FAIL_OK
 
 
-# We do not support explicit global evals through <global>.eval(...).
-js1_5/Regress/regress-68498-003: FAIL_OK
-
-
 # No support for toSource().
 js1_5/Regress/regress-248444: FAIL_OK
 js1_5/Regress/regress-313967-01: FAIL_OK
 js1_5/Regress/regress-313967-02: FAIL_OK
 
 # This fails because we don't have stack space for Function.prototype.apply
 # with very large numbers of arguments.  The test uses 2^24 arguments.
 js1_5/Array/regress-350256-03: FAIL_OK
 
 
@@ skipping 179 matching lines @@
 
 # Expects top level arguments (passed on command line?) to be
 # the empty string?
 js1_5/Regress/regress-336100: FAIL_OK
 
 
 # Regular expression test failures due to PCRE. We match KJS (ie, perl)
 # behavior and not the ECMA spec.
 ecma_3/RegExp/15.10.2-1: FAIL_OK
 ecma_3/RegExp/perlstress-001: FAIL_OK
-ecma_3/RegExp/regress-334158: FAIL_OK
+ecma_3/RegExp/regress-334158: PASS || FAIL
 
 
 # This test requires a failure if we try to compile a function with more
 # than 65536 arguments.  This seems to be a Mozilla restriction.
 js1_5/Regress/regress-290575: FAIL_OK
 
 
 # Fails because of the way function declarations are
 # handled in V8/KJS. V8 follows IE behavior and introduce
 # all nested function declarations when entering the
@@ skipping 67 matching lines @@
 js1_5/Regress/regress-303213: FAIL
 
 
 # Bug 1202592: New ecma_3/String/15.5.4.11 is failing.
 ecma_3/String/15.5.4.11: FAIL
 
 # Bug 1202597: New js1_5/Expressions/regress-394673 is failing.
 # Marked as: Will not fix. V8 throws an acceptable RangeError.
 js1_5/Expressions/regress-394673: FAIL
 
-# Bug 1202598: New mozilla test js1_5/Regress/regress-383682 fails.
-js1_5/Regress/regress-383682: FAIL
-
-
 ##################### MOZILLA EXTENSION TESTS #####################
 
 ecma/extensions/15.1.2.1-1: FAIL_OK
 ecma_3/extensions/regress-385393-03: FAIL_OK
 ecma_3/extensions/7.9.1: FAIL_OK
 js1_5/extensions/catchguard-001: FAIL_OK
 js1_5/extensions/catchguard-002: FAIL_OK
 js1_5/extensions/catchguard-003: FAIL_OK
 js1_5/extensions/getset-001: FAIL_OK
 js1_5/extensions/getset-003: FAIL_OK
@@ skipping 195 matching lines @@
 ecma/Date/15.9.5.8: SKIP
 ecma/Date/15.9.5.9: SKIP
 ecma/Date/15.9.5.10-2: SKIP
 ecma/Date/15.9.5.11-2: SKIP
 ecma/Expressions/11.7.2: SKIP
 ecma/Expressions/11.10-2: SKIP
 ecma/Expressions/11.7.3: SKIP
 ecma/Expressions/11.10-3: SKIP
 ecma/Expressions/11.7.1: SKIP
 ecma_3/RegExp/regress-209067: SKIP