Report out of memory if we cannot allocate memory for the deoptimization table.
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 3 Jun 2011 10:11:10 +0000 (10:11 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 3 Jun 2011 10:11:10 +0000 (10:11 +0000)
commit945bd3e70cdb1f5e2585e346d816050eceaa96b9
treec5e9c26bac863c63b2b60ff0e5902e9066706ed9
parenteee5e6c3fc766e7120cc5ce7934474f21b13a609
Report out of memory if we cannot allocate memory for the deoptimization table.

Currently we pass a null pointer to memcpy. We will crash either way,
but going through FatalProcessOutOfMemory makes it clear what is going
on.

R=kmillikin@chromium.org
BUG=http://crbug.com/84717

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8163 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/deoptimizer.cc