AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

[turbofan] Temporary workaround for JSInliner zone.

Browse Source 
This is exactly what it looks like. A temporary hack that ensures we
can make forward progress with the JSInliner despite other components
have a hard time picking the correct zone. This hack is a hack!

R=bmeurer@chromium.org,jarin@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#31380}
This commit is contained in:
mstarzinger 2015-10-19 08:09:04 -07:00 committed by Commit bot
parent fb8a97eed9
commit 68a74034f2
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/compiler/js-inlining.cc
View File

@ -318,8 +318,12 @@ Reduction JSInliner::ReduceJSCallFunction(Node* node,
return NoChange(); return NoChange();
} }
Zone zone; // TODO(mstarzinger): The correct thing would be to use a local zone here for
ParseInfo parse_info(&zone, function); // the inner graph. This however leads to Zone-Types being allocated in the
// wrong zone and makes the engine explode at high speeds. Explosion bad!
// Zone zone;
// ParseInfo parse_info(&zone, function);
ParseInfo parse_info(jsgraph_->zone(), function);
CompilationInfo info(&parse_info); CompilationInfo info(&parse_info);
if (info_->is_deoptimization_enabled()) { if (info_->is_deoptimization_enabled()) {
info.MarkAsDeoptimizationEnabled(); info.MarkAsDeoptimizationEnabled();