After more feedback on the write barriers in the baseline JIT, it's time to clean up some the DFG write barrier code.
Created attachment 219725 [details] Patch
Comment on attachment 219725 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=219725&action=review > Source/JavaScriptCore/dfg/DFGSpeculativeJIT.cpp:5483 > -MacroAssembler::Call SpeculativeJIT::storeToWriteBarrierBuffer(CCallHelpers& jit, GPRReg cell, GPRReg scratch1, GPRReg scratch2) > +MacroAssembler::Call SpeculativeJIT::storeToWriteBarrierBuffer(CCallHelpers& jit, GPRReg cell, GPRReg scratch1, GPRReg scratch2, ScratchRegisterAllocator& allocator) This method exists just for Repatch, right? In that case, we should definitely move it out of SpeculativeJIT.
(In reply to comment #2) > (From update of attachment 219725 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=219725&action=review > > > Source/JavaScriptCore/dfg/DFGSpeculativeJIT.cpp:5483 > > -MacroAssembler::Call SpeculativeJIT::storeToWriteBarrierBuffer(CCallHelpers& jit, GPRReg cell, GPRReg scratch1, GPRReg scratch2) > > +MacroAssembler::Call SpeculativeJIT::storeToWriteBarrierBuffer(CCallHelpers& jit, GPRReg cell, GPRReg scratch1, GPRReg scratch2, ScratchRegisterAllocator& allocator) > > This method exists just for Repatch, right? > > In that case, we should definitely move it out of SpeculativeJIT. Should it just go into Repatch itself?
Committed r160919: <http://trac.webkit.org/changeset/160919>
*** Bug 126012 has been marked as a duplicate of this bug. ***