Reimplement the padding of relocation information for lazy deoptimization on ia32.
The previous implementation attempted to keep track of the needed relocation size for deoptimization while generating the optimized code. That was error prone. This patch moves the relocation resizing to the deoptimizer as the last step of creating an optimized code object. The down side to this approach is that two relocation information byte arrays are created for all optimized functions that do not have enough relocation space for lazy deoptimization. R=sgjesse@chromium.org Review URL: http://codereview.chromium.org/6730050 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7360 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
Showing
Please
register
or
sign in
to comment