1. 20 Nov, 2017 1 commit
  2. 15 Nov, 2017 1 commit
  3. 14 Nov, 2017 1 commit
    • Ross McIlroy's avatar
      [compiler] Add background compilation mode. · 9a4b334f
      Ross McIlroy authored
      Adds support for compiling top-level code on a background thread behind a flag.
      When the flag is enabled, any background-parsing-task will perform compilation
      as well as parsing.
      
      BUG=v8:5203
      TBR=marja@chromium.org,mstarzinger@chromium.org
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Icf90ac7211298d3555515dafc7c3245618ec1304
      Reviewed-on: https://chromium-review.googlesource.com/764048
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49364}
      9a4b334f
  4. 03 Nov, 2017 2 commits
  5. 17 Oct, 2017 1 commit
  6. 13 Oct, 2017 1 commit
  7. 26 Sep, 2017 1 commit
    • Yang Guo's avatar
      [snapshot] add kProduceExhaustiveCodeCache option. · 7f9de3dc
      Yang Guo authored
      - Add kProduceExhaustiveCodeCache to v8::ScriptCompiler::CompileOptions
        to request eager compilation to add as much as possible to the code
        cache for the script.
      - Repurpose ParseInfo::kLazy flag.
      - Remove ParseInfo::kDebug flag.
      - Remove --serialize-toplevel as it has become obsolete.
      
      R=marja@chromium.org
      
      Bug: chromium:768705
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Ife14f7a1d1c02e525f0b9dbfd2452013d67c7167
      Reviewed-on: https://chromium-review.googlesource.com/684019
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48160}
      7f9de3dc
  8. 21 Aug, 2017 1 commit
    • Ross McIlroy's avatar
      [Parsing] Always pass a valid character-stream into the parser · 1bc01952
      Ross McIlroy authored
      Changes the contract of the parser to have a valid character stream passed
      in the ParseInfo rather than the current situation where either:
       - it is passed explicitly (e.g., for streaming scripts)
       - a Script is passed and a character stream is created for this
       - or a source and encoding is passed in ParseInfo and the character stream
         is created from this.
      
      The parse info also now owns the character stream (in a unique_ptr). It
      can be destroyed using a new ResetCharacterStream() function. This will
      enable the character stream to be kept live if any functions are asm.js
      modules which were parsed, in order to be reused by the asm.js parser.
      
      BUG=v8:5203
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Ifda167391b2eadb38ebf9fcb2f565d2ed9ea3c6f
      Reviewed-on: https://chromium-review.googlesource.com/616767
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47474}
      1bc01952
  9. 14 Aug, 2017 1 commit
  10. 10 Aug, 2017 1 commit
  11. 04 May, 2017 1 commit
  12. 03 May, 2017 1 commit
  13. 02 May, 2017 1 commit
  14. 28 Mar, 2017 1 commit
  15. 24 Mar, 2017 1 commit
  16. 09 Feb, 2017 1 commit
  17. 07 Feb, 2017 5 commits
  18. 24 Jan, 2017 1 commit
  19. 20 Jan, 2017 3 commits
  20. 17 Oct, 2016 1 commit
  21. 13 Oct, 2016 2 commits
  22. 11 Oct, 2016 1 commit
  23. 07 Oct, 2016 1 commit
  24. 15 Sep, 2016 2 commits
    • jochen's avatar
      Only pass the outer scope info with ParseInfo · 65aa596f
      jochen authored
      We don't need the context anymore for parsing, the scope info chain is
      enough.
      
      BUG=v8:5215
      R=marja@chromium.org,jgruber@chromium.org,mstarzinger@chromium.org
      
      Review-Url: https://codereview.chromium.org/2342443004
      Cr-Commit-Position: refs/heads/master@{#39457}
      65aa596f
    • jochen's avatar
      Fully deserialize the scope chain after parsing, not before · 94492437
      jochen authored
      To avoid a dependency on the heap during parsing, we only create a scope chain
      without linking to the associated ScopeInfo objects before parsing. This is
      enough to avoid special cases during parsing of arrow functions / eval.
      
      Looking at the outer scope's variables during parsing was only needed for hosting
      sloppy block functions inside eval. To be able to do this now, we hoist for the
      outer-most eval scope after parsing, in DeclarationScope::Analyze.
      
      DeclarationScope::Analyze is also where we replace the outer scope chain with the
      fully deserialized version, so variables can be resolved.
      
      Also, this unifies background and foreground thread parsing, as we don't have to
      worry about ScopeInfos getting accessed before we're back on the main thread.
      
      BUG=v8:5215
      R=verwaest@chromium.org,marja@chromium.org,adamk@chromium.org
      
      Review-Url: https://codereview.chromium.org/2306413002
      Cr-Commit-Position: refs/heads/master@{#39452}
      94492437
  25. 12 Sep, 2016 1 commit
  26. 02 Sep, 2016 1 commit
  27. 23 Aug, 2016 1 commit
  28. 03 Aug, 2016 1 commit
  29. 29 Jul, 2016 1 commit
  30. 28 Jul, 2016 1 commit
  31. 25 Jul, 2016 1 commit