Add more generic version of reloc info padding to ensure enough space for reloc patch...
authorricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 22 Feb 2011 12:28:33 +0000 (12:28 +0000)
committerricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 22 Feb 2011 12:28:33 +0000 (12:28 +0000)
commit45c63ffa6a7b7be643c89cef631f19af02c367d4
tree0aaae31f881a89254a5d9dd946c3ef7c46194ee7
parent8162d9029db62e6aeccbcf3514d9715fca57caa9
Add more generic version of reloc info padding to ensure enough space for reloc patching during deoptimization (fixes issue 1174).

The old version only added extra space when we did indirect calls, but
the problem remains the same with normal calls that can be represented
as a single byte. When doing patching each call will always be at
least 2 bytes long because we use RUNTIME_ENTY as the reloc mode.

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

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