RESOLVED FIXED 106058
DFG::ByteCodeCache serves little or no purpose ever since we decided to keep bytecode around permanently 
https://bugs.webkit.org/show_bug.cgi?id=106058
Summary DFG::ByteCodeCache serves little or no purpose ever since we decided to keep ...
Filip Pizlo
Reported 2013-01-03 15:49:06 PST
ByteCodeCache used to be great because we would by default throw away the instruction stream of code blocks at the earliest opportunity. ByteCodeCache would allow the DFG to reparse code blocks on demand, regenerating the instruction stream if necessary. But now we always keep the instruction stream around. Hence, all we really need to be doing is asking the executable for the baseline code block. The bytecode parser already does this, and its insistence on distinguishing between the code block and the profiled block is unnecessary for inlinees.
Attachments
the patch (15.84 KB, patch)
2013-01-03 15:50 PST, Filip Pizlo 		msaboff: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Filip Pizlo
Comment 1 2013-01-03 15:50:36 PST
Created attachment 181241 [details] the patch
Filip Pizlo
Comment 2 2013-01-03 16:29:46 PST
Landed in http://trac.webkit.org/changeset/138763
Note You need to log in before you can comment on or make changes to this bug.