1. 10 Aug, 2022 34 commits
  2. 09 Aug, 2022 6 commits
    • Dominik Inführ's avatar
      [heap] Remove IncrementalMarking::StartBlackAllocationForTesting · de5dbbe5
      Dominik Inführ authored
      Black allocation is already enabled when starting incremental marking.
      
      Bug: v8:12775
      Change-Id: I492c3ab89a3a3251ab005d2f3fc4ee46f28f5615
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3820067
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#82321}
      de5dbbe5
    • Adam Klein's avatar
      Revert "Reland "[turbofan] Support Phi nodes in SL Verifier"" · 32f4b268
      Adam Klein authored
      This reverts commit 97d1ab6c.
      
      Reason for revert: simplified lowering verifier crashes on GPU bots:
      https://ci.chromium.org/ui/p/v8/builders/ci/Linux%20V8%20FYI%20Release%20(NVIDIA)/20848/overview
      
      Original change's description:
      > Reland "[turbofan] Support Phi nodes in SL Verifier"
      >
      > This reverts commit 82a876b0.
      >
      > Bug: v8:13086, v8:12619
      > Change-Id: Idcc42f36b642fefb3ed706214e7385cccc89effc
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3779687
      > Auto-Submit: Nico Hartmann <nicohartmann@chromium.org>
      > Commit-Queue: Nico Hartmann <nicohartmann@chromium.org>
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#82285}
      
      Bug: v8:13086, v8:12619
      Change-Id: I7a2fb19eb752403337d45de0a7ca02a5d8842766
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3820904
      Auto-Submit: Adam Klein <adamk@chromium.org>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/main@{#82320}
      32f4b268
    • Dominik Inführ's avatar
      [heap] Reorganize IncrementalMarking::TryMarkingComplete() · e4eba195
      Dominik Inführ authored
      This CL tries to improve readability of TryMarkingComplete() by
      splitting it up into multiple smaller methods.
      
      It also removes StepResult::kWaitingForFinalization since this was
      only used in one test which could easily be rewritten to not need this
      value. This makes CombineStepResult() and Step()s return value simpler
      to understand.
      
      Bug: v8:12775
      Change-Id: I981bc7b736246ab53058d1e61e3c67db0d1130b7
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3816668Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#82319}
      e4eba195
    • Milad Fa's avatar
      PPC: [codegen] Change a few DCHECKs to V8_ASSUMEs · 036384d0
      Milad Fa authored
      Port e5524920
      
      Original Commit Message:
      
          This might or might not give clang-tidy a hint that the reported case
          (see issue) cannot happen. It might also generate slightly better code
          by giving hints to the compiler.
          Note that V8_ASSUME is actually a DCHECK in DEBUG builds, so we do not
          loose any checks here.
      
          Some DCHECKs were removed because they are redundant
          (RegisterBase::code() assumes to be only called on valid registers).
      
      R=clemensb@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com
      BUG=
      LOG=N
      
      Change-Id: I653d398eb4b6b10fa769de62a9900edda95dd5db
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3820583
      Commit-Queue: Milad Farazmand <mfarazma@redhat.com>
      Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
      Cr-Commit-Position: refs/heads/main@{#82318}
      036384d0
    • Milad Fa's avatar
      PPC/s390: [ext-code-space] Add InterpreterEntryTrampolineForProfiling builtin · 30d6b245
      Milad Fa authored
      Port 1067c6ac
      
      Original Commit Message:
      
          ... - a code range size agnostic version of InterpreterEntryTrampoline
          builtin. The new builtin is fully compatible with the default version
          and used as a template for creating interpreter entry trampoline
          Code objects when --interpreted-frames-native-stack is enabled.
      
          This CL introduces a new assembler option "position_independent_code"
          which affects the way builtin calls are generated.
          This mode is enabled only for InterpreterEntryTrampolineForProfiling.
      
          Motivation:
      
          * InterpreterEntryTrampoline uses RelocInfo::CODE_TARGET for calling
            other builtins which requires the code range to be small enough to
            allow PC-relative jumps/calls between Code objects. This is the
            reason why --interpreted-frames-native-stack was not supported on
            arm and might not work on arm64 because the code range is bigger
            than the max PC-relative distance for call/jump instructions.
            The new builtin calls other builtins via builtins entry table which
            makes the code fully relocatable and usable for any code range size.
      
          * RelocInfo::CODE_TARGET requires a target code to be materialized
            as a Code object which contradicts the Code-less builtins goal.
      
          * The --interpreted-frames-native-stack is rarely used in the wild but
            we have to pay the price of deserializing InterpreterEntryTrampoline
            builtin as a Code object which consumes address space in the code
            range and thus limits the number of V8 isolates that can be created
            because of code range exhaustion. Now the pointer compression cage
            becomes the limiting factor instead of the code range.
      
          * We can remove complicated logic of Factory::CopyCode() and respective
            support on GC side.
      
      R=ishell@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com
      BUG=
      LOG=N
      
      Change-Id: I2ed5edbffc5c33717f4becf8370369f7a4d000fb
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3816765Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
      Commit-Queue: Milad Farazmand <mfarazma@redhat.com>
      Cr-Commit-Position: refs/heads/main@{#82317}
      30d6b245
    • Michael Lippautz's avatar
      [heap] Remove dead code · 9e2b4aee
      Michael Lippautz authored
      Change-Id: I18190e902929d5b513b0a897faaddb8750f9b27a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3820066
      Auto-Submit: Michael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#82316}
      9e2b4aee