-
yangguo@chromium.org authored
If OSR happens before regular recompilation, the unoptimized function code on the stack may not have deoptimization support. In that case, graph creation compiles the unoptimized code again to include support. That code is then installed as shared code. When we patch code for OSR, the function code on the stack and not the shared code is what we want. R=titzer@chromium.org TEST=block-conflicts.js with --always-osr --concurrent-osr Review URL: https://codereview.chromium.org/99013003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18261 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
96b58ba4
Name |
Last commit
|
Last update |
---|---|---|
benchmarks | ||
build | ||
include | ||
samples | ||
src | ||
test | ||
tools | ||
.clang-format | ||
.gitignore | ||
AUTHORS | ||
ChangeLog | ||
DEPS | ||
LICENSE | ||
LICENSE.strongtalk | ||
LICENSE.v8 | ||
LICENSE.valgrind | ||
Makefile | ||
Makefile.android | ||
Makefile.nacl | ||
OWNERS | ||
PRESUBMIT.py | ||
WATCHLISTS |