1. 27 Dec, 2019 1 commit
  2. 13 Dec, 2019 1 commit
  3. 28 Nov, 2019 1 commit
  4. 22 Oct, 2019 1 commit
  5. 16 Sep, 2019 1 commit
  6. 13 Sep, 2019 2 commits
  7. 09 Sep, 2019 1 commit
  8. 20 May, 2019 1 commit
  9. 15 May, 2019 1 commit
  10. 06 Mar, 2019 1 commit
  11. 26 Feb, 2019 1 commit
  12. 04 Feb, 2019 2 commits
  13. 15 Jan, 2019 1 commit
  14. 10 Jan, 2019 1 commit
  15. 18 Dec, 2018 1 commit
    • Ross McIlroy's avatar
      [Compiler] Fix flaky tsan error for bytecode flushing. · 1a5d6a53
      Ross McIlroy authored
      The SFI's flags can be changed by the mutator while the concurrent marker is checking
      the flags for bytecode flushing. None of the flag bits checked for bytecode flushing
      are changed, however since they are in an int32 field TSAN will complain if any of the
      other flags are changed while reading from another flag. Fix this by making the flags
      use the RELAXED_INT32_ACCESSORS.
      
      BUG=v8:8592,v8:8395
      
      Change-Id: I5fbb4fd381c2b288abf0cd36eb0b8256e1929af6
      Reviewed-on: https://chromium-review.googlesource.com/c/1382458Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#58325}
      1a5d6a53
  16. 13 Dec, 2018 1 commit
  17. 17 Oct, 2018 1 commit
  18. 07 Sep, 2018 4 commits
  19. 24 Jul, 2018 1 commit
  20. 06 Jul, 2018 1 commit
  21. 05 Jul, 2018 1 commit
  22. 22 Jun, 2018 1 commit
  23. 08 May, 2018 1 commit
  24. 09 Apr, 2018 1 commit
  25. 06 Apr, 2018 1 commit
  26. 08 Dec, 2017 1 commit
  27. 07 Dec, 2017 1 commit
  28. 06 Oct, 2017 1 commit
  29. 27 Jul, 2017 1 commit
  30. 17 Jul, 2017 1 commit
  31. 14 Jul, 2017 1 commit
    • Alexey Kozyatinskiy's avatar
      [inspector] improve return position of explicit return in non-async function · 08965860
      Alexey Kozyatinskiy authored
      Goal of this CL: explicit return from non-async function has position after
      return expression as return position (will unblock [1]).
      
      BytecodeArrayBuilder has SetStatementPosition and SetExpressionPosition methods.
      If one of these methods is called then next generated bytecode will get passed
      position. It's general treatment for most cases.
      Unfortunately it doesn't work for Returns:
      - debugger requires source positions exactly on kReturn bytecode in stepping
        implementation,
      - BytecodeGenerator::BuildReturn and BytecodeGenerator::BuildAsyncReturn
        generates more then one bytecode and general solution will put return position
        on first generated bytecode,
      - it's not easy to split BuildReturn function into two parts to allow something
        like following in BytecodeGenerator::VisitReturnStatement since generated
        bytecodes are actually controlled by execution_control().
      ..->BuildReturnPrologue();
      ..->SetReturnPosition(stmt);
      ..->Return();
      
      In this CL we pass ReturnStatement through ExecutionControl and use it for
      position when we emit return bytecode right here.
      
      So this CL only will improve return position for returns inside of non-async
      functions, I'll address async functions later.
      
      [1] https://chromium-review.googlesource.com/c/543161/
      
      Change-Id: Iede512c120b00c209990bf50c20e7d23dc0d65db
      Reviewed-on: https://chromium-review.googlesource.com/560738
      Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46687}
      08965860
  32. 13 Jul, 2017 1 commit
  33. 12 Jul, 2017 1 commit
  34. 08 Jun, 2017 1 commit
  35. 07 Jun, 2017 1 commit