Here is what happens in debug-multiple-breakpoints.js:
1. A hot function is marked for optimization by replacing its code with
CompileOptimized or CompileOptimizedConcurrent builtin.
2. Debug::PrepareForBreakPoints deoptimizes optimized functions but doesn't
restore code of functions that were marked for optimization.
3. ASSERT_EQ(Code::FUNCTION, function->code()->kind()) triggers in
Debug::MaybeRecompileFunctionForDebugging
Yang, is this a bug in Debug::PrepareForBreakPoints that functions marked
for
optimization do not get their code restored?
https://codereview.chromium.org/271543004/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
