Remove a brittle assertion from Turbofan lazy deoptimization handling.
authorjarin@chromium.org <jarin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 13 Aug 2014 11:46:05 +0000 (11:46 +0000)
committerjarin@chromium.org <jarin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 13 Aug 2014 11:46:05 +0000 (11:46 +0000)
commitb80e76841eb9bcdefb1d8ef7c08fc390d6c39f76
tree47bd51f17a9021b69ddaa886fe2fcbb581320406
parent1b17f59b5db7f1c3e1996cdc3cd1f73eab1159ed
Remove a brittle assertion from Turbofan lazy deoptimization handling.

As discussed in person with Benedikt, it is better to remove the assertion because it is too brittle. The assertion says that the continuation block should immediately follow the call. However, there are exceptions - such as nop or constant pool in-between being fine - that make the assertion brittle.

BUG=
R=mstarzinger@chromium.org

Review URL: https://codereview.chromium.org/471523002

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23102 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/compiler/arm/code-generator-arm.cc
src/compiler/arm64/code-generator-arm64.cc
src/compiler/code-generator.cc
src/compiler/code-generator.h
src/compiler/ia32/code-generator-ia32.cc
src/compiler/x64/code-generator-x64.cc
test/cctest/cctest.status