1. 31 Oct, 2018 4 commits
  2. 19 Oct, 2018 1 commit
  3. 11 Oct, 2018 2 commits
  4. 10 Oct, 2018 1 commit
  5. 26 Sep, 2018 1 commit
  6. 20 Sep, 2018 1 commit
  7. 23 Jul, 2018 1 commit
  8. 20 Jul, 2018 1 commit
  9. 16 Jul, 2018 1 commit
  10. 08 May, 2018 1 commit
  11. 14 Apr, 2018 1 commit
    • Jakob Kummerow's avatar
      [ubsan] Change Address typedef to uintptr_t · 2459046c
      Jakob Kummerow authored
      The "Address" type is V8's general-purpose type for manipulating memory
      addresses. Per the C++ spec, pointer arithmetic and pointer comparisons
      are undefined behavior except within the same array; since we generally
      don't operate within a C++ array, our general-purpose type shouldn't be
      a pointer type.
      
      Bug: v8:3770
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
      Change-Id: Ib96016c24a0f18bcdba916dabd83e3f24a1b5779
      Reviewed-on: https://chromium-review.googlesource.com/988657
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52601}
      2459046c
  12. 01 Mar, 2018 1 commit
    • Clemens Hammacher's avatar
      Fix is_trivially_copyable check for MSVC and older stdlibc++ · 9dd6f0d0
      Clemens Hammacher authored
      MSVC 2015 and 2017 implement std::is_trivially_copyable, but not
      correctly. Hence, reimplement it using more low-level primitives.
      
      For stdlibc++ versions below 5.0, we already have a workaround for the
      missing support of std::is_trivially_copyable, but this is an unsound
      approximation, because it is ignoring move constructor, move assignment
      and copy assignment. Therefore, do not use this approximation for
      asserting trivial copyability of a type.
      
      Finally, add unittests for the new is_trivially_copyable
      implementations.
      
      R=mstarzinger@chromium.org
      CC=loorongjie@gmail.com
      
      Change-Id: I9ee56a65882e8c94b72c9a2d484edd27963a5d89
      Reviewed-on: https://chromium-review.googlesource.com/941521Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51651}
      9dd6f0d0
  13. 29 Jan, 2018 1 commit
  14. 18 Oct, 2017 1 commit
  15. 13 Oct, 2017 1 commit
  16. 28 Sep, 2017 1 commit
    • Peter Marshall's avatar
      [cleanup] Replace List with std::vector in api. · 329f6946
      Peter Marshall authored
      The members of HandleScopeImplementer are copied with memcpy when
      the isolate is transferred to another thread. List contained some
      primitives which allowed us to manually free the backing store, which
      was needed in order to ensure that threads would not hold on to
      old pointers and use them later. With std::vector, we can't do that.
      
      Here we change the HandleScopeImplementer to instead use a custom
      structure DetachableVector, which contains a std::vector but allows
      manual detaching and freeing of the backing store. This allows us to
      maintain the old behavior.
      
      Bug: v8:6333
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I6361d161cdb19878ba19ed51d6ba2fae99e8cdc0
      Reviewed-on: https://chromium-review.googlesource.com/660125Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48197}
      329f6946
  17. 11 Sep, 2017 1 commit
  18. 08 Aug, 2017 1 commit
  19. 31 Jul, 2017 1 commit
  20. 20 Jun, 2017 1 commit
  21. 05 Apr, 2017 1 commit
  22. 22 Feb, 2017 1 commit
  23. 17 Oct, 2016 1 commit
  24. 01 Apr, 2016 1 commit
  25. 26 Oct, 2015 3 commits
  26. 20 Aug, 2015 1 commit
  27. 15 Jul, 2015 3 commits
  28. 22 Jun, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Revive the VectorSlotPair and also put feedback on JSCallFunction. · d4f70f8c
      bmeurer authored
      We resurrect the VectorSlotPair in order to be able to separate the
      feedback input for the compiler from the actual type feedback vector
      that is required to meet the IC requirements at runtime. This will allow
      us to for example use feedback from a different context or divide the
      type feedback vector into two separate vectors, without having to touch
      the compiler. It'll allow use to load the vector from the shared
      function info at runtime, while still consuming feedback in the
      compiler (i.e. we don't rely on the feedback vector node to be a heap
      constant).
      
      R=mvstanton@chromium.org
      
      Review URL: https://codereview.chromium.org/1198983002
      
      Cr-Commit-Position: refs/heads/master@{#29185}
      d4f70f8c
  29. 01 Jun, 2015 1 commit
  30. 05 May, 2015 2 commits
  31. 04 Aug, 2014 1 commit