Skip to content

V
V8
Switch branch/tag
  1. 16 Jul, 2014 1 commit
    • vogelheim@chromium.org's avatar
      Change ScriptCompiler::CompileOptions to allow for two 'cache' modes · a42612b4
      vogelheim@chromium.org authored 
      (parser or code) and to be explicit about cache consumption or production
(rather than making presence of cached_data imply one or the other.)

Also add a --cache flag to d8, to allow testing the functionality.

-----------------------------
API change

Reason: Currently, V8 supports a 'parser cache' for repeatedly executing the same script. We'd like to add a 2nd mode that would cache code, and would like to let the embedder decide which mode they chose (if any).

Note: Previously, the 'use cached data' property was implied by the presence of the cached data itself. (That is, kNoCompileOptions and source->cached_data != NULL.) That is no longer sufficient, since the presence of data is no longer sufficient to determine /which kind/ of data is present.

Changes from old behaviour:

- If you previously didn't use caching, nothing changes.
Example:
  v8::CompileUnbound(isolate, source, kNoCompileOptions);

- If you previously used caching, it worked like this:

  - 1st run:
  v8::CompileUnbound(isolate, source, kProduceToCache);
  Then, source->cached_data would contain the
  data-to-be cached. This remains the same, except you
  need to tell V8 which type of data you want.
  v8::CompileUnbound(isolate, source, kProduceParserCache);

  - 2nd run:
  v8::CompileUnbound(isolate, source, kNoCompileOptions);
  with source->cached_data set to the data you received in
  the first run. This will now ignore the cached data, and
  you need to explicitly tell V8 to use it:
  v8::CompileUnbound(isolate, source, kConsumeParserCache);
-----------------------------

BUG=
R=marja@chromium.org, yangguo@chromium.org

Review URL: https://codereview.chromium.org/389573006

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22431 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a42612b4
  3. 07 Jul, 2014 1 commit
  5. 30 Jun, 2014 1 commit
  7. 23 Jun, 2014 1 commit
  9. 10 Jun, 2014 1 commit
  11. 05 Jun, 2014 1 commit
    • vogelheim@chromium.org's avatar
      Support external startup data in V8. · ba9f391b
      vogelheim@chromium.org authored 
      [Retry of crrev.com/293993021, which caused problems with 'ninja all' in Chromium. First patch set if a clean apply
of crrev.com/293993021. Subsequent sets are the actual fix
for that issue.]

If the embedder chooses, the 'natives' (library sources) and the
precompiled startup blob can be written to files during the build
process and handed over to V8 at startup. The main purpose would be
to reduce the size of the compiled binary for space constrained
platforms.

The build-time option is off by default. Nothing should change if
it's not enabled.

BUG=
R=jochen@chromium.org

Review URL: https://codereview.chromium.org/315033002

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21696 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      ba9f391b
  13. 04 Jun, 2014 1 commit
  15. 03 Jun, 2014 2 commits
  17. 27 May, 2014 4 commits
  19. 14 May, 2014 1 commit
  21. 13 May, 2014 1 commit
  23. 29 Apr, 2014 1 commit
  25. 25 Apr, 2014 1 commit
  27. 25 Mar, 2014 1 commit
  29. 10 Jan, 2014 2 commits
  31. 09 Jan, 2014 1 commit
  33. 22 Nov, 2013 1 commit
  35. 21 Nov, 2013 1 commit
  37. 18 Nov, 2013 1 commit
  39. 24 Oct, 2013 6 commits
  41. 04 Oct, 2013 1 commit
  43. 02 Sep, 2013 1 commit
  45. 29 Aug, 2013 1 commit
  47. 27 Aug, 2013 1 commit
  49. 02 Aug, 2013 1 commit
  51. 31 Jul, 2013 1 commit
  53. 30 Jul, 2013 1 commit
  55. 23 Jul, 2013 1 commit
  57. 05 Jun, 2013 1 commit
  59. 08 May, 2013 1 commit