Skip to content

V
V8
Switch branch/tag
  1. 06 Aug, 2014 1 commit
  3. 04 Aug, 2014 1 commit
  5. 30 Jul, 2014 1 commit
  7. 24 Jul, 2014 1 commit
  9. 23 Jul, 2014 1 commit
  11. 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
  13. 10 Jul, 2014 1 commit
  15. 08 Jul, 2014 1 commit
  17. 30 Jun, 2014 1 commit
  19. 24 Jun, 2014 1 commit
  21. 18 Jun, 2014 1 commit
  23. 16 Jun, 2014 1 commit
  25. 13 Jun, 2014 1 commit
  27. 03 Jun, 2014 1 commit
  29. 12 May, 2014 2 commits
  31. 09 May, 2014 2 commits
  33. 02 May, 2014 1 commit
  35. 30 Apr, 2014 1 commit
  37. 29 Apr, 2014 1 commit
  39. 25 Apr, 2014 1 commit
  41. 22 Apr, 2014 1 commit
  43. 17 Apr, 2014 1 commit
  45. 11 Apr, 2014 1 commit
  47. 19 Mar, 2014 1 commit
  49. 17 Mar, 2014 1 commit
  51. 14 Mar, 2014 1 commit
  53. 13 Mar, 2014 1 commit
  55. 11 Mar, 2014 2 commits
  57. 07 Mar, 2014 2 commits
  59. 28 Feb, 2014 2 commits
  61. 13 Feb, 2014 1 commit
    • vegorov@chromium.org's avatar
      Improve positions tracking inside the HGraphBuilder. · 8f170a66
      vegorov@chromium.org authored 
      Instead of tracking simple absolute offset from the start of the script like other places do, track a pair of (inlining id, offset from the start of inlined function).

This enables us to pinpoint with inlining path an instruction came from. Previously in multi-script environments we emitted positions that made very little sense because inside a single optimized function they would point to different scripts without a way to distinguish them.

Start dumping the source of every inlined function to make possible IR viewing tools with integrated source views as there was previously no way to acquire this information from IR dumps. We also dump source position at which each inlining occured.

Tracked positions are written into hydrogen.cfg as pos:<inlining-id>_<offset>.

Flag --emit-opt-code-positions is renamed by this change into --hydrogen-track-positions to better convey it's meaning.

In addition this change assigned global unique identifier to each optimization performed inside isolate. This allows to precisely match compilation artifacts (e.g. IR and disassembly) and deoptimizations.

BUG=
R=yangguo@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19360 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      8f170a66
  63. 10 Feb, 2014 1 commit
  65. 14 Jan, 2014 1 commit
  67. 23 Dec, 2013 1 commit
  69. 05 Dec, 2013 1 commit