1. 28 Mar, 2017 1 commit
  2. 07 Feb, 2017 5 commits
  3. 24 Jan, 2017 1 commit
  4. 20 Jan, 2017 3 commits
  5. 09 Jan, 2017 1 commit
  6. 30 Nov, 2016 1 commit
  7. 18 Nov, 2016 1 commit
    • marja's avatar
      Remove FLAG_min_preparse_length. · 4a5b7e32
      marja authored
      It originates from the era where we used to run a separate preparse step
      before parsing and store the function data. Now the usage of preparser
      is something completely different, so this flag doesn't make sense any
      more.
      
      In addition, this way we get more test coverage for preparser (for small
      scripts).
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2513563002
      Cr-Commit-Position: refs/heads/master@{#41110}
      4a5b7e32
  8. 17 Oct, 2016 1 commit
  9. 07 Oct, 2016 1 commit
  10. 22 Aug, 2016 1 commit
  11. 29 Jun, 2016 1 commit
  12. 08 Jun, 2016 1 commit
  13. 01 Apr, 2016 1 commit
  14. 26 Nov, 2015 1 commit
  15. 14 Aug, 2015 1 commit
    • vogelheim's avatar
      Rework startup-data-util. · c69e2eae
      vogelheim authored
      - Make the API look like v8::V8::InitializeICU.
        (That is: A static method call, not an object to be created on the stack.)
      - Fix path separator on Windows, by calling base::OS::isPathSeparator.
      - Move into API, so that it can be called by hello-world & friends.
      - Actually call it from hello-world and friends.
      
      R=jochen@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/1292053002
      
      Cr-Commit-Position: refs/heads/master@{#30174}
      c69e2eae
  16. 10 Jul, 2015 1 commit
  17. 06 Jul, 2015 1 commit
  18. 15 May, 2015 1 commit
  19. 29 Apr, 2015 1 commit
  20. 28 Apr, 2015 1 commit
  21. 12 Mar, 2015 1 commit
  22. 09 Mar, 2015 1 commit
  23. 12 Feb, 2015 1 commit
    • marja's avatar
      Parsing: Make Parser not know about Isolate during background parsing. · df0cb999
      marja authored
      Parser must be able to operate independent of Isolate and the V8 heap during
      parsing. After the heap-independent phase, there is a heap dependent phase,
      during which we internalize strings, handle errors, etc.
      
      This makes Isolate (also via CompilationInfo) unaccessible during parsing, and
      thus decreases the probability of accidental code changes which would add
      heap-dependent operations into the heap-independent phase.
      
      Since Isolate is also accessible via CompilationInfo, now CompilationInfo is
      only passed to the entry points of parsing, and not stored in Parser.
      
      R=rossberg@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/908173003
      
      Cr-Commit-Position: refs/heads/master@{#26612}
      df0cb999
  24. 19 Sep, 2014 1 commit
  25. 18 Sep, 2014 2 commits
  26. 10 Sep, 2014 1 commit
  27. 04 Aug, 2014 1 commit
  28. 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
  29. 03 Jul, 2014 2 commits
  30. 30 Jun, 2014 1 commit
  31. 24 Jun, 2014 1 commit
  32. 18 Jun, 2014 1 commit