Fix assert triggered in fast/regex/pcre-test-4.html We were not filtering out
authorerik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 3 May 2012 08:22:12 +0000 (08:22 +0000)
committererik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 3 May 2012 08:22:12 +0000 (08:22 +0000)
commitbaf7ebd6dad86d1fdd8758fb30d119d36f9b1c3a
treed0033e34a77a50af6e01f8e7ad1d712e3bd382bc
parent10b0eee0d0b109cc2d0002eef2ac91543d09fcc1
Fix assert triggered in fast/regex/pcre-test-4.html We were not filtering out
all the nodes that had non-ASCII characters.  That has been fixed, but because
of the protection against over-deep recursion when filtering it is wrong to
assert that all nodes were filtered.  This change therefore also makes sure we
can cope with non-filtered nodes by adding back some code removed in
https://chromiumcodereview.appspot.com/10174017/
Review URL: https://chromiumcodereview.appspot.com/10358008

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11487 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/jsregexp.cc
test/mjsunit/regexp-capture-3.js