Add the possibility for a code stub to be non-movable
authorsgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 9 Mar 2011 10:38:19 +0000 (10:38 +0000)
committersgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 9 Mar 2011 10:38:19 +0000 (10:38 +0000)
commit061fa8be1168a714d54f144a789eef09515f6fef
tree51c35c2a03c8543ea66c85219cf66b1ce001b65d
parentdf7bbc23863acc149bcabffe7d08bbd34d986bef
Add the possibility for a code stub to be non-movable

Non-moveable code-stube are allocated in large object space. They are only required on ARM where the different C-entry stubs are required to never move.

This gets rid of pre-computing these stubs and hope that they never move. Also for crankshaft the C-entry stub which saved doubles is not generated in the snapshot so it ends up being generated at runtime and potentially move.
Review URL: http://codereview.chromium.org/6626072

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7097 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arm/code-stubs-arm.cc
src/arm/code-stubs-arm.h
src/code-stubs.cc
src/code-stubs.h
src/factory.cc
src/factory.h
src/heap.cc
src/heap.h
src/ia32/code-stubs-ia32.cc
src/x64/code-stubs-x64.cc