I went ahead and submitted this -- sorry about the inconvenience. To get it back into your workspace use:
$ svn merge -c -1429 . Cheers, Kasper On Thu, Mar 5, 2009 at 2:10 PM, <[email protected]> wrote: > Reviewers: Erik Corry, Lasse Reichstein, Mads Ager, > > Message: > This is actually quite annoying and kinda dramatic and it is not > something we *need* to do right away, but I'd like to get the known > crasher (likely introduced in 1383) out of the bleeding_edge branch soon > to make it possible to start testing the new compiler that landed on > bleeding_edge in revision 1389. > > Please advice on how you want to proceed. > > Description: > Revert revisions 1383, 1384, 1391, 1398, 1401, 1402, > 1418, and 1419 from bleeding_edge until we have a fix > for the crashers we see on the distributed test infra- > structure. > > We know that revision 1383 is causing issues, but I > had to revert some of the other recent RegExp changes > in order to get this part out. > > Please review this at http://codereview.chromium.org/39186 > > SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ > > Affected files: > M src/factory.h > M src/factory.cc > M src/jsregexp.h > M src/jsregexp.cc > M src/macros.py > M src/objects-debug.cc > M src/objects-inl.h > M src/objects.h > M src/objects.cc > M src/regexp-delay.js > M src/runtime.h > M src/runtime.cc > M src/string.js > M test/mjsunit/regexp-static.js > D test/mjsunit/regexp-string-methods.js > D test/mjsunit/regress/regress-254.js > M tools/js2c.py > > > --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
