sgjesse@chromium.org 10bb16f495 Add support for lazy deoptimization from deferred stack checks ... The debugger can be entered from the deferred stack check in optimized code. This can cause both lazy deoptimization and debugger deoptimization (setting the first break point and inspecting the stack for optimized code respectively). This required deoptimization support from the deferred stack check. The lazy deoptimiztion call is inserted when the deferred code is done including restoring the registers. The bailout to the full code is the begining of the loop body as that is where the stack check is sitting in the optimized code. The bailout is not to the stack check in the full code as that is sitting at the end of the loop. R=kmillikin@chromium.org BUG=none TEST=none Review URL: http://codereview.chromium.org//7212025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8535 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2011-07-05 13:21:29 +00:00
..
benchmarks	Change cctests to use variant flags as part of the name for the serilization file.	2011-03-21 12:57:25 +00:00
cctest	Add support for lazy deoptimization from deferred stack checks	2011-07-05 13:21:29 +00:00
es5conform	Reapply 7763, including arm and x64 variants.	2011-05-05 05:21:30 +00:00
message	Change cctests to use variant flags as part of the name for the serilization file.	2011-03-21 12:57:25 +00:00
mjsunit	Fix bug 1529: check for NULL handle in v8::TryCatch::StackTrace.	2011-07-04 13:29:56 +00:00
mozilla	Updated test expectations of future reserved keyword tests.	2011-06-24 16:54:47 +00:00
preparser	Revert r8516.	2011-07-01 15:44:21 +00:00
sputnik	Do not pass the global object as the receiver to strict-mode and	2011-06-30 12:29:19 +00:00
test262	Bring test262 expectations up-to-date.	2011-04-11 13:54:30 +00:00