1. 10 Nov, 2017 1 commit
  2. 08 Nov, 2017 1 commit
  3. 07 Nov, 2017 1 commit
  4. 06 Nov, 2017 1 commit
  5. 02 Nov, 2017 3 commits
    • Ulan Degenbaev's avatar
      Reland "[heap] Temporarily disable concurrent marking." · 586067e4
      Ulan Degenbaev authored
      This is a reland of a9a50dc9
      
      Buildbot crashes are fixed by a274fc65.
      
      Original change's description:
      > [heap] Temporarily disable concurrent marking.
      > 
      > The 6.3 branch has a data race that is fixed in 6.4 but the fix is too
      > large for back merging.
      > 
      > This CL will be back-merged to 6.3 after getting Canary coverage.
      > 
      > Concurrent marking will be re-enabled afterwards.
      > 
      > Bug: chromium:774644
      > Change-Id: I4112da0e133a637cc4fb52dee2e4c165cdc74f1f
      > Reviewed-on: https://chromium-review.googlesource.com/749811
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#49080}
      
      Bug: chromium:774644
      Change-Id: Idf5d179eca25a1481c70c6ca3bccde4869deb544
      Reviewed-on: https://chromium-review.googlesource.com/751271Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49090}
      586067e4
    • Ulan Degenbaev's avatar
      Revert "[heap] Temporarily disable concurrent marking." · 49c62872
      Ulan Degenbaev authored
      This reverts commit a9a50dc9.
      
      Reason for revert: buildbot crashes.
      
      Original change's description:
      > [heap] Temporarily disable concurrent marking.
      > 
      > The 6.3 branch has a data race that is fixed in 6.4 but the fix is too
      > large for back merging.
      > 
      > This CL will be back-merged to 6.3 after getting Canary coverage.
      > 
      > Concurrent marking will be re-enabled afterwards.
      > 
      > Bug: chromium:774644
      > Change-Id: I4112da0e133a637cc4fb52dee2e4c165cdc74f1f
      > Reviewed-on: https://chromium-review.googlesource.com/749811
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#49080}
      
      TBR=ulan@chromium.org,hpayer@chromium.org,mlippautz@chromium.org
      
      Change-Id: Ia9d2128c01b811073c1c8f0392eb13b7d7745cd1
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:774644
      Reviewed-on: https://chromium-review.googlesource.com/751501Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49083}
      49c62872
    • Ulan Degenbaev's avatar
      [heap] Temporarily disable concurrent marking. · a9a50dc9
      Ulan Degenbaev authored
      The 6.3 branch has a data race that is fixed in 6.4 but the fix is too
      large for back merging.
      
      This CL will be back-merged to 6.3 after getting Canary coverage.
      
      Concurrent marking will be re-enabled afterwards.
      
      Bug: chromium:774644
      Change-Id: I4112da0e133a637cc4fb52dee2e4c165cdc74f1f
      Reviewed-on: https://chromium-review.googlesource.com/749811Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49080}
      a9a50dc9
  6. 20 Oct, 2017 1 commit
  7. 19 Oct, 2017 2 commits
  8. 17 Oct, 2017 1 commit
  9. 11 Oct, 2017 1 commit
  10. 05 Oct, 2017 1 commit
  11. 29 Sep, 2017 5 commits
  12. 28 Sep, 2017 2 commits
  13. 22 Sep, 2017 1 commit
  14. 21 Sep, 2017 3 commits
  15. 15 Sep, 2017 1 commit
  16. 29 Aug, 2017 1 commit
  17. 28 Aug, 2017 1 commit
  18. 23 Aug, 2017 1 commit
  19. 02 Aug, 2017 1 commit
  20. 18 Jul, 2017 1 commit
  21. 14 Jul, 2017 1 commit
  22. 27 Jun, 2017 1 commit
  23. 26 Jun, 2017 1 commit
  24. 23 Jun, 2017 1 commit
  25. 14 Jun, 2017 1 commit
  26. 02 Jun, 2017 1 commit
  27. 30 May, 2017 1 commit
  28. 29 May, 2017 1 commit
  29. 23 May, 2017 1 commit
  30. 16 May, 2017 1 commit
    • Leszek Swirski's avatar
      [ignition] Change --trace-ignition to a runtime flag · 4becbe34
      Leszek Swirski authored
      Generate the code (extra runtime calls) for --trace-ignition support at
      compile time, based on a #define (similar to TRACE_MAPS). Then check for
      --trace-ignition at run-time when deciding whether to actually print
      anything. This should make --trace-ignition less painful to use.
      
      Note that --trace-igition is disabled by default, even on debug builds.
      It has to be enabled with the gn arg "v8_enable_trace_ignition=true"
      
      As a drive-by, TRACE_MAPS is renamed to V8_TRACE_MAPS, for consistency,
      and SFI unique index (needed both by --trace-ignition and --trace-maps)
      is cleaned up to be behind another #define.
      
      Change-Id: I8dd0c62d0e6b7ee9c75541d45eb729dc03acbee9
      Reviewed-on: https://chromium-review.googlesource.com/506203
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45346}
      4becbe34