Skip to content

V
V8
Switch branch/tag
  1. 14 Oct, 2014 1 commit
  3. 29 Sep, 2014 1 commit
  5. 19 Sep, 2014 1 commit
  7. 18 Sep, 2014 2 commits
  9. 17 Sep, 2014 1 commit
  11. 16 Sep, 2014 3 commits
  13. 15 Sep, 2014 1 commit
    • jochen@chromium.org's avatar
      Currently, a new isolate is created in an uninitialized state, and · 65a18578
      jochen@chromium.org authored 
      several API methods will automatically initialize it. During this
uninitialized state, code event handlers and function entry handlers can
be attached to the isolate.

This CL deprecates SetFunctionEntryHook and moves the configuration of
those handlers to the Isolate factory method.

This will allow for initializing the Isolate at creation time in the
future.

Users of V8::SetFunctionEntryHook should pass the entry hook to
Isolate::New instead. V8::SetJitCodeEventHandler should either be passed
to Isolate::New as well, or (if startup events are not required) invoked
via the Isolate.

BUG=none
LOG=y
R=svenpanne@chromium.org

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

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23940 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      65a18578
  15. 02 Sep, 2014 1 commit
  17. 27 Aug, 2014 1 commit
  19. 12 Aug, 2014 1 commit
  21. 04 Aug, 2014 1 commit
  23. 24 Jul, 2014 1 commit
  25. 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
  27. 10 Jul, 2014 3 commits
  29. 09 Jul, 2014 1 commit
  31. 07 Jul, 2014 1 commit
  33. 03 Jul, 2014 2 commits
  35. 30 Jun, 2014 1 commit
  37. 27 Jun, 2014 1 commit
  39. 23 Jun, 2014 1 commit
  41. 20 Jun, 2014 2 commits
  43. 10 Jun, 2014 1 commit
  45. 05 Jun, 2014 2 commits
  47. 04 Jun, 2014 1 commit
  49. 03 Jun, 2014 2 commits
  51. 28 May, 2014 1 commit
  53. 27 May, 2014 4 commits
  55. 26 May, 2014 1 commit