forked from WebKit/WebKit-http
-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
JSCell::m_gcData should encode its information differently
https://bugs.webkit.org/show_bug.cgi?id=129741 Reviewed by Geoffrey Garen. We want to keep track of three GC states for an object: 1. Not marked (which implies not in the remembered set) 2. Marked but not in the remembered set 3. Marked and in the remembered set Currently we only indicate marked vs. not marked in JSCell::m_gcData. During a write barrier, we only want to take the slow path if the object being stored to is in state #2. We'd like to make the test for state #2 as fast as possible, which means making it a compare against 0. * dfg/DFGOSRExitCompilerCommon.cpp: (JSC::DFG::osrWriteBarrier): * dfg/DFGSpeculativeJIT.cpp: (JSC::DFG::SpeculativeJIT::checkMarkByte): (JSC::DFG::SpeculativeJIT::writeBarrier): * dfg/DFGSpeculativeJIT.h: * dfg/DFGSpeculativeJIT32_64.cpp: (JSC::DFG::SpeculativeJIT::writeBarrier): * dfg/DFGSpeculativeJIT64.cpp: (JSC::DFG::SpeculativeJIT::writeBarrier): * ftl/FTLLowerDFGToLLVM.cpp: (JSC::FTL::LowerDFGToLLVM::allocateCell): (JSC::FTL::LowerDFGToLLVM::emitStoreBarrier): * heap/Heap.cpp: (JSC::Heap::clearRememberedSet): (JSC::Heap::addToRememberedSet): * jit/AssemblyHelpers.h: (JSC::AssemblyHelpers::checkMarkByte): * jit/JIT.h: * jit/JITPropertyAccess.cpp: (JSC::JIT::checkMarkByte): (JSC::JIT::emitWriteBarrier): * jit/Repatch.cpp: (JSC::writeBarrier): * llint/LowLevelInterpreter.asm: * llint/LowLevelInterpreter32_64.asm: * llint/LowLevelInterpreter64.asm: * runtime/JSCell.h: (JSC::JSCell::mark): (JSC::JSCell::remember): (JSC::JSCell::forget): (JSC::JSCell::isMarked): (JSC::JSCell::isRemembered): * runtime/JSCellInlines.h: (JSC::JSCell::JSCell): * runtime/StructureIDBlob.h: (JSC::StructureIDBlob::StructureIDBlob): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@165135 268f45cc-cd09-0410-ab3c-d52691b4dbfc
- Loading branch information
1 parent
3442637
commit 4015971
Showing
19 changed files
with
140 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,59 @@ | ||
2014-03-05 Mark Hahnenberg <[email protected]> | ||
|
||
JSCell::m_gcData should encode its information differently | ||
https://bugs.webkit.org/show_bug.cgi?id=129741 | ||
|
||
Reviewed by Geoffrey Garen. | ||
|
||
We want to keep track of three GC states for an object: | ||
|
||
1. Not marked (which implies not in the remembered set) | ||
2. Marked but not in the remembered set | ||
3. Marked and in the remembered set | ||
|
||
Currently we only indicate marked vs. not marked in JSCell::m_gcData. During a write | ||
barrier, we only want to take the slow path if the object being stored to is in state #2. | ||
We'd like to make the test for state #2 as fast as possible, which means making it a | ||
compare against 0. | ||
|
||
* dfg/DFGOSRExitCompilerCommon.cpp: | ||
(JSC::DFG::osrWriteBarrier): | ||
* dfg/DFGSpeculativeJIT.cpp: | ||
(JSC::DFG::SpeculativeJIT::checkMarkByte): | ||
(JSC::DFG::SpeculativeJIT::writeBarrier): | ||
* dfg/DFGSpeculativeJIT.h: | ||
* dfg/DFGSpeculativeJIT32_64.cpp: | ||
(JSC::DFG::SpeculativeJIT::writeBarrier): | ||
* dfg/DFGSpeculativeJIT64.cpp: | ||
(JSC::DFG::SpeculativeJIT::writeBarrier): | ||
* ftl/FTLLowerDFGToLLVM.cpp: | ||
(JSC::FTL::LowerDFGToLLVM::allocateCell): | ||
(JSC::FTL::LowerDFGToLLVM::emitStoreBarrier): | ||
* heap/Heap.cpp: | ||
(JSC::Heap::clearRememberedSet): | ||
(JSC::Heap::addToRememberedSet): | ||
* jit/AssemblyHelpers.h: | ||
(JSC::AssemblyHelpers::checkMarkByte): | ||
* jit/JIT.h: | ||
* jit/JITPropertyAccess.cpp: | ||
(JSC::JIT::checkMarkByte): | ||
(JSC::JIT::emitWriteBarrier): | ||
* jit/Repatch.cpp: | ||
(JSC::writeBarrier): | ||
* llint/LowLevelInterpreter.asm: | ||
* llint/LowLevelInterpreter32_64.asm: | ||
* llint/LowLevelInterpreter64.asm: | ||
* runtime/JSCell.h: | ||
(JSC::JSCell::mark): | ||
(JSC::JSCell::remember): | ||
(JSC::JSCell::forget): | ||
(JSC::JSCell::isMarked): | ||
(JSC::JSCell::isRemembered): | ||
* runtime/JSCellInlines.h: | ||
(JSC::JSCell::JSCell): | ||
* runtime/StructureIDBlob.h: | ||
(JSC::StructureIDBlob::StructureIDBlob): | ||
|
||
2014-03-05 Filip Pizlo <[email protected]> | ||
|
||
More FTL ARM fixes | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.