Make sure we always have room for patching the reloc info during lazy deoptimization...
authorricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 15 Feb 2011 14:36:12 +0000 (14:36 +0000)
committerricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 15 Feb 2011 14:36:12 +0000 (14:36 +0000)
commita8d4360d65e2089ee94eb660f22c14f9a2fcaa89
tree32e35580924c6df2980cc6b5ce30026b52c02558
parentb4fd72b3354fe2361ef9015c0e2a66fcfdfca678
Make sure we always have room for patching the reloc info during lazy deoptimization (fixes issue 1156).

Before we could have calls to builtins that would not be in the
relocation info since this used a register as target. Whenever we have
this case (from lithium codegen) we now emit a comment in the reloc
info.

Review URL: http://codereview.chromium.org/6499015

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6795 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/assembler.cc
src/assembler.h
src/ia32/assembler-ia32.cc
src/ia32/assembler-ia32.h
src/ia32/deoptimizer-ia32.cc
src/ia32/lithium-codegen-ia32.cc
test/mjsunit/regress/regress-1156.js [new file with mode: 0644]