1. 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
  2. 18 Aug, 2017 1 commit
  3. 09 Aug, 2017 1 commit
  4. 07 Aug, 2017 2 commits
  5. 04 Aug, 2017 1 commit
  6. 03 Aug, 2017 1 commit
  7. 31 Jul, 2017 1 commit
  8. 28 Jul, 2017 1 commit
  9. 27 Jul, 2017 4 commits
  10. 26 Jul, 2017 1 commit
  11. 21 Jul, 2017 1 commit
  12. 19 Jul, 2017 1 commit
  13. 04 Jul, 2017 1 commit
  14. 06 Jun, 2017 1 commit
    • Igor Sheludko's avatar
      [parser] Introduce SharedFunctionInfo::has_shared_name(). · 9a2c18f5
      Igor Sheludko authored
      Properly propagate the fact that the function has a statically known name from
      parser to SharedFunctionInfo objects. The empty string that has been set as
      name before this CL does not help to distinguish cases like:
        var o1 = { ''(){} };
        var o1 = { [foo()](){} };
      or
        var o2 = { get ''(){} };
        var o2 = { get [foo()](){} };
      
      This is a preliminary step for using different layouts for closure objects with
      and without computed names.
      
      TBR=bmeurer@chromium.org, marja@chromium.org
      
      Bug: v8:6459
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I10afa6f4bda7881c3714711a75f720f83c1d875d
      Reviewed-on: https://chromium-review.googlesource.com/522073
      Commit-Queue: Igor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45744}
      9a2c18f5
  15. 22 May, 2017 1 commit
  16. 04 May, 2017 1 commit
  17. 03 May, 2017 1 commit
  18. 02 May, 2017 1 commit
  19. 19 Apr, 2017 1 commit
    • Adam Klein's avatar
      Remove "calls eval" bit from ParseInfo and PreParseData · 9b512732
      Adam Klein authored
      There's no reason to keep track, for a preparsed function itself,
      whether that function calls eval. All that matters is that the ancestor
      scopes are marked as having an inner scope which calls eval. The function
      will have its "calls eval" bit persisted if/when it's fully parsed.
      
      The only "behavioral" change in this patch is the removal of a DCHECK.
      
      Bug: v8:6092
      Change-Id: I17e396c8a265030fe0ad941707e4a97972e6650b
      Reviewed-on: https://chromium-review.googlesource.com/481223
      Commit-Queue: Adam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#44732}
      9b512732
  20. 11 Apr, 2017 1 commit
  21. 10 Apr, 2017 1 commit
  22. 28 Mar, 2017 2 commits
  23. 27 Mar, 2017 1 commit
  24. 22 Mar, 2017 1 commit
  25. 10 Feb, 2017 6 commits
  26. 07 Feb, 2017 5 commits