c5eb79e6aa
Now that we have an API to request code cache, we want to decouple compilation from serialization. As a first step, we will add CompileEager option (used when we want to produce full code cache) and DeferredProduceCodeOption to NoCacheReason. This is so that we can properly bucket the compilation time and collect statistics about the cache behaviour. Once, blink and node start using the new API, we can remove the code to produce code cache from the compilation. Bug: chromium:783124 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I35dbb6b0af39940450d412ff75b769603398b2f6 Reviewed-on: https://chromium-review.googlesource.com/828977 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50336} |
||
---|---|---|
.. | ||
libplatform | ||
APIDesign.md | ||
DEPS | ||
OWNERS | ||
PRESUBMIT.py | ||
v8-debug.h | ||
v8-inspector-protocol.h | ||
v8-inspector.h | ||
v8-platform.h | ||
v8-profiler.h | ||
v8-testing.h | ||
v8-util.h | ||
v8-value-serializer-version.h | ||
v8-version-string.h | ||
v8-version.h | ||
v8.h | ||
v8config.h |