1. 04 Nov, 2019 5 commits
    • Dan Elphick's avatar
      [heap] Enable Verify for RO_SPACE when it is shared · fea98b6f
      Dan Elphick authored
      This re-enables verification for RO_SPACE when V8_SHARED_RO_HEAP is
      defined. This required refactoring PagedSpaceObjectIterator and methods
      in its calling chain to explicitly pass the PagedSpace and Heap pointers
      through as they cannot be obtained from the Page in this mode.
      
      Also removes unused Page::Print() method.
      
      Bug: v8:7464
      Change-Id: Ibc2c147a7bde6723f43bbaf93cf1db93e76c611e
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1893350Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#64722}
      fea98b6f
    • Sigurd Schneider's avatar
      [heap-profiler] Improve reporting for WeakMap entries · 05eb0e41
      Sigurd Schneider authored
      This CL improves reporting for WeakMap entries: If a retaining chain
      goes through a WeakMap entry (i.e. key and weak map are alive, and keep
      value alive) then both the key and the value are reported. Additionally
      the phrasing is clarified, such that entries in retaining paths are
      easier to understand.
      
      Bug: chromium:1020096
      Change-Id: Ib05cd6f7939c6de41b554c682ad1fbf685b87608
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1893335Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#64721}
      05eb0e41
    • Ulan Degenbaev's avatar
      [profiler] Make ulan@ an owner of heap related files in src/profiler · c0d21ab1
      Ulan Degenbaev authored
      Change-Id: I7993bf1d27c0b7a148e776c7c2eddf4ebe76da6e
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1892951Reviewed-by: 's avatarPeter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#64720}
      c0d21ab1
    • Michaël Zasso's avatar
      [compiler] Explicitly initialize const members · 50031fae
      Michaël Zasso authored
      This fixes a compilation error in Node.js with Xcode:
      
      initialize the const member 'blueprint_'.
      
      error: constructor for 'v8::internal::compiler::Callee' must explicitly
      Change-Id: Ia55398428d0de35a9ad5132eabd22d0adb694514
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1895561
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#64719}
      50031fae
    • Mu Tao's avatar
      [mips] Reland "[compiler] Optionally apply an offset to stack checks" · 75f376ad
      Mu Tao authored
      Port b875f466
      
      Original Commit Message:
      
          Reland "[compiler] Optionally apply an offset to stack checks"
      
          This is a reland of 4a16305b
      
          The original CL adjust only one part of the stack check, namely the
          comparison of the stack pointer against the stack limit in generated code.
          There is a second part: Runtime::kStackGuard repeats this check to
          distinguish between a stack overflow and an interrupt request.
      
          This second part in runtime must apply the offset just like in generated
          code. It is implemented in this reland by the StackCheckOffset operator
          and a new StackGuardWithGap runtime function.
      
          Original change's description:
          > [compiler] Optionally apply an offset to stack checks
          >
          > The motivation behind this change is that the frame size of an optimized
          > function and its unoptimized version may differ, and deoptimization
          > may thus trigger a stack overflow. The solution implemented in this CL
          > is to optionally apply an offset to the stack check s.t. the check
          > becomes 'sp - offset > limit'. The offset is applied to stack checks at
          > function-entry, and is set to the difference between the optimized and
          > unoptimized frame size.
          >
          > A caveat: OSR may not be fully handled by this fix since we've already
          > passed the function-entry stack check. A possible solution would be to
          > *not* skip creation of function-entry stack checks for inlinees.
          >
          > This CL: 1. annotates stack check nodes with the stack check kind, where
          > kind is one of {function-entry,iteration-body,unknown}. 2. potentially
          > allocates a temporary register to store the result of the 'sp - offset'
          > in instruction selection (and switches input registers to 'unique'
          > mode). 3. Applies the offset in code generation.
          >
          > mode). 3. Applies the offset in code generation.
          >
          > Drive-by: Add src/compiler/globals.h for compiler-specific globals.
          >
          > Bug: v8:9534,chromium:1000887
          > Change-Id: I257191c4a4978ccb60cfa5805ef421f30f0e9826
          > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1762521
          > Commit-Queue: Jakob Gruber <jgruber@chromium.org>
          > Reviewed-by: Georg Neis <neis@chromium.org>
          > Cr-Commit-Position: refs/heads/master@{#63701}
      
      Change-Id: I77554bddde57153ec92c4b80c15d0a52efbaab2d
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1893554Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Commit-Queue: Mu Tao <pamilty@gmail.com>
      Cr-Commit-Position: refs/heads/master@{#64718}
      75f376ad
  2. 03 Nov, 2019 1 commit
  3. 01 Nov, 2019 10 commits
  4. 31 Oct, 2019 24 commits