Fix assertion failure due to too many deoptimization ids.
authorfschneider@chromium.org <fschneider@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 20 Mar 2012 08:49:23 +0000 (08:49 +0000)
committerfschneider@chromium.org <fschneider@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 20 Mar 2012 08:49:23 +0000 (08:49 +0000)
commitb0bb4f078a7c0b9d16f42890a8c86e085db96d33
treee0e80e4e6136227237dff1e3b85d2ec4a7f6be15
parentde9120500a1cfaa9acc3600c864be9a6157b5081
Fix assertion failure due to too many deoptimization ids.

The failing mozilla test was caused by more deoptimizations
introduced by --always-opt and r11087.

We abort code generation in release mode, so we should do
the same in debug mode.
Review URL: https://chromiumcodereview.appspot.com/9752004

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11091 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arm/lithium-codegen-arm.cc
src/ia32/lithium-codegen-ia32.cc
src/mips/lithium-codegen-mips.cc
src/x64/lithium-codegen-x64.cc