Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(958)

Unified Diff: src/builtins/mips64/builtins-mips64.cc

Issue 2448933002: [compiler] Make SFI "optimize" flag a "tier up" flag (Closed)
Patch Set: Rebase Created 4 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: src/builtins/mips64/builtins-mips64.cc
diff --git a/src/builtins/mips64/builtins-mips64.cc b/src/builtins/mips64/builtins-mips64.cc
index ea94066563f958fa9727d578ed1c91aa3540f773..5882080f17a80d0e0ee73fa0cead03406891eb57 100644
--- a/src/builtins/mips64/builtins-mips64.cc
+++ b/src/builtins/mips64/builtins-mips64.cc
@@ -1473,12 +1473,10 @@ void Builtins::Generate_CompileLazy(MacroAssembler* masm) {
__ pop(argument_count);
__ ld(entry, FieldMemOperand(closure, JSFunction::kSharedFunctionInfoOffset));
// Is the shared function marked for optimization?
- __ lbu(a5,
- FieldMemOperand(
- entry, SharedFunctionInfo::kWasMarkedForOptimizationByteOffset));
- __ And(
- a5, a5,
- Operand(1 << SharedFunctionInfo::kWasMarkedForOptimizationBitWithinByte));
+ __ lbu(a5, FieldMemOperand(
+ entry, SharedFunctionInfo::kWasMarkedForTierUpByteOffset));
+ __ And(a5, a5,
+ Operand(1 << SharedFunctionInfo::kWasMarkedForTierUpBitWithinByte));
__ Branch(&gotta_call_runtime_no_stack, ne, a5, Operand(zero_reg));
// Is the full code valid?
__ ld(entry, FieldMemOperand(entry, SharedFunctionInfo::kCodeOffset));

Powered by Google App Engine
This is Rietveld 408576698