1. 23 May, 2019 1 commit
  2. 15 Feb, 2019 1 commit
  3. 09 Nov, 2018 1 commit
  4. 06 Nov, 2018 1 commit
  5. 17 Oct, 2018 1 commit
  6. 04 Jul, 2018 1 commit
  7. 30 Nov, 2017 1 commit
  8. 28 Nov, 2017 1 commit
  9. 23 Nov, 2017 1 commit
  10. 23 Oct, 2017 1 commit
  11. 29 Aug, 2017 2 commits
  12. 26 Jul, 2017 1 commit
  13. 13 Jun, 2017 1 commit
  14. 17 May, 2017 1 commit
    • Marja Hölttä's avatar
      [parser|ast] Simplify AstNodeFactory Zone usage. · f270bbfa
      Marja Hölttä authored
      AstNodeFactory used to get the Zone directly from AstValueFactory. But that's
      generally the wrong Zone (the main Zone, instead of the temp Zone), and the
      creator of AstNodeFactory had to call set_zone right after. By adding a Zone
      param, we can pass the correct Zone right away.
      
      Also made PreParserFactory have an AstNodeFactory, so that we don't need to
      create temporary AstNodeFactories all the time.
      
      Also removed AstNodeFactory::BodyScope since DiscardableZoneScope essentially
      did the same thing already.
      
      BUG=v8:5516,v8:6092
      
      Change-Id: I189d2e6afe91c91e49d8ed7e3496a0d9c405e1c5
      Reviewed-on: https://chromium-review.googlesource.com/507129
      Commit-Queue: Marja Hölttä <marja@chromium.org>
      Reviewed-by: 's avatarDaniel Vogelheim <vogelheim@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45370}
      f270bbfa
  15. 27 Mar, 2017 1 commit
  16. 24 Mar, 2017 1 commit
  17. 28 Feb, 2017 1 commit
  18. 17 Jan, 2017 1 commit
    • leszeks's avatar
      [ast] Remove internalization before AST rewriting · bb71555e
      leszeks authored
      This internalization was not necessary, since the rewriting does not use
      the .result name string.
      
      The subsequent internalization is still needed, so to simplify later
      refactoring, this CL also adds "releasing" of the disallow scopes and
      uses them here immediately before the second internalize. Notably, this
      means that the rewriting is now also in the disallow scopes.
      
      Driveby: Remove isolate from the rewriter's processor constructor.
      
      BUG=v8:5832
      
      Review-Url: https://codereview.chromium.org/2635913002
      Cr-Commit-Position: refs/heads/master@{#42403}
      bb71555e
  19. 16 Jan, 2017 1 commit
  20. 09 Jan, 2017 2 commits
  21. 05 Dec, 2016 1 commit
  22. 24 Oct, 2016 1 commit
    • verwaest's avatar
      Simplify and fix the rewriter · caba112d
      verwaest authored
      Now we
      - always set .result to undefined before a visited loop and switch since we can't know whether they will set a value,
      - only visit finally if it can break/continue; and only store/restore .result in that case
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2427253003
      Cr-Commit-Position: refs/heads/master@{#40542}
      caba112d
  23. 21 Oct, 2016 1 commit
  24. 20 Sep, 2016 1 commit
  25. 05 Sep, 2016 2 commits
  26. 22 Aug, 2016 1 commit
  27. 05 Aug, 2016 3 commits
  28. 01 Aug, 2016 1 commit
    • verwaest's avatar
      Always finalize blocks after parsing, also for do-expressions · f02018ce
      verwaest authored
      Rather than finalizing after rewriting do-expressions, we rewrite in the
      outer scope if the block scope was finalized. Rewriting do expressions
      cannot introduce any new nodes that requires the block to stay around,
      so finalizing before and after is equivalent. (Only a temporary is
      introduced which always ends up in a ClosureScope)
      
      BUG=v8:5209
      R=rossberg@chromium.org, caitpotter88@gmail.com, adamk@chromium.org
      
      Review-Url: https://codereview.chromium.org/2167713004
      Cr-Commit-Position: refs/heads/master@{#38193}
      f02018ce
  29. 15 Jul, 2016 1 commit
    • verwaest's avatar
      Templatize AstVisitor with its subclass · ebf166df
      verwaest authored
      This replaces the vtable on AstNode with a NodeType tag. The visitors replace double dispatch with a single switch over the NodeType.
      
      For now, visitors with subclasses still have virtual methods themselves. We should probably specialize them later as well.
      
      The uint8_t NodeType allows us to better pack memory, saving 8-16 bytes on many AST nodes (with additional packing that I'll do in a follow-up CL)
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2142233003
      Cr-Commit-Position: refs/heads/master@{#37788}
      ebf166df
  30. 30 Jun, 2016 1 commit
  31. 01 Mar, 2016 1 commit
    • yangguo's avatar
      [debugger] fix break locations for assignments and return. · d9fe836d
      yangguo authored
      We used to emit debug break location on block entry. This cannot be
      ported to the interpreted as we do not emit bytecode for block entry.
      This made no sense to begin with though, but accidentally added
      break locations for var declarations.
      
      With this change, the debugger no longer breaks at var declarations
      without initialization. This is in accordance with the fact that the
      interpreter does not emit bytecode for uninitialized var declarations.
      
      Also fix the bytecode to match full-codegen's behavior wrt return
      positions:
      - there is a break location before the return statement, with the source
        position of the return statement.
      - right before the actual return, there is another break location. The
        source position points to the end of the function.
      
      R=rmcilroy@chromium.org, vogelheim@chromium.org
      TBR=rossberg@chromium.org
      BUG=v8:4690
      LOG=N
      
      Review URL: https://codereview.chromium.org/1744123003
      
      Cr-Commit-Position: refs/heads/master@{#34388}
      d9fe836d
  32. 18 Feb, 2016 1 commit
    • rossberg's avatar
      [es6] Implement for-of iterator finalization · cb1bf4af
      rossberg authored
      Implements iterator finalisation by desugaring for-of loops with an additional try-finally wrapper. See comment in parser.cc for details.
      
      Also improved some AST printing facilities while there.
      
      @Ross, I had to disable the bytecode generation test for for-of, because it got completely out of hand after this change (the new bytecode has 150+ lines). See the TODO that I assigned to you.
      
      Patch set 1 is WIP patch by Georg (http://crrev.com/1695583003), patch set 2 relative changes.
      
      @Georg, FYI, I changed the following:
      
      - Moved try-finally out of the loop body, for performance, and in order to be able to handle `continue` correctly.
      - Fixed scope management in ParseForStatement, which was the cause for the variable allocation failure.
      - Fixed pre-existing zone initialisation bug in rewriter, which caused the crashes.
      - Enabled all tests, adjusted a few others, added a couple more.
      
      BUG=v8:2214
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1695393003
      
      Cr-Commit-Position: refs/heads/master@{#34111}
      cb1bf4af
  33. 04 Feb, 2016 1 commit
    • neis's avatar
      [generators] Desugar yield*. · 5269944a
      neis authored
      This CL deals with yield* by desugaring it in the parser.  Hence the
      full-codegen implementation of it becomes obsolete and can be removed in a
      future CL.
      
      The only change in semantics should be that the results of the iterator's next
      and throw methods are checked to be objects, which didn't happen before but is
      required by the spec.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/1643903003
      
      Cr-Commit-Position: refs/heads/master@{#33735}
      5269944a
  34. 03 Feb, 2016 1 commit
  35. 26 Nov, 2015 1 commit