1. 08 Jun, 2022 1 commit
    • Samuel Groß's avatar
      [sandbox] Implement sandbox crash filter · 059903de
      Samuel Groß authored
      If enabled, a signal handler is installed which intercepts memory access
      violations (e.g. SIGSEGV) and checks whether they occurred inside the
      sandbox address space, in which case the process is terminated cleanly
      as this does not represent a (security) issue with the sandbox. However,
      if the access violation occurred outside the sandbox, the access
      violation is forwarded to the original signal handler.
      
      The filter can be enabled in d8 by specifying
      --enable-sandbox-crash-filter.
      
      Bug: v8:12878
      Change-Id: If9d76267e90ee79ee81ab793d7774afed6226b7c
      Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688408Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Commit-Queue: Samuel Groß <saelo@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#80999}
      059903de
  2. 25 May, 2022 1 commit
  3. 13 May, 2022 1 commit
  4. 02 May, 2022 1 commit
  5. 27 Apr, 2022 1 commit
  6. 13 Apr, 2022 1 commit
  7. 07 Apr, 2022 1 commit
  8. 05 Apr, 2022 1 commit
    • Clemens Backes's avatar
      [wasm] Fix interrupt of empty loop · 43232bf0
      Clemens Backes authored
      This includes two fixes:
      1. For dynamic tiering, the budget must always be reduced when jumping
         backwards, otherwise we might never trigger tier up, which makes the
         loop non-interruptible (because the tier-up check replaces the stack
         check).
      2. The d8 worker implementation also needs to terminate the isolate via
         an interrupt, in addition to scheduling a task, because the worker
         might never return to the event queue.
      
      This CL also fixes one of the failure modes of the inspector fuzzer
      (see https://crbug.com/1180018).
      
      R=jkummerow@chromium.org, marja@chromium.org
      
      Bug: v8:12767, chromium:1180018
      
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      Change-Id: Ia01d1725fc14931d2ea54c4769c4ee93f866ed63
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3568470Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79773}
      43232bf0
  9. 18 Mar, 2022 1 commit
  10. 18 Feb, 2022 1 commit
  11. 26 Jan, 2022 3 commits
    • Shu-yu Guo's avatar
      Reland^2 "[string] Support shared strings in Value{Serializer,Deserializer}" · fc23bc1d
      Shu-yu Guo authored
      This is a reland of 5320fe8d
      
      Changes since revert:
      - Remove stale DCHECK in deserializer
      
      Original change's description:
      > Reland "[string] Support shared strings in Value{Serializer,Deserializer}"
      >
      > This is a reland of 3cb4039c
      >
      > Changes since revert:
      > - Fix FLAG_stress_scavenge interaction with shared Isolate
      > - Use the shared Isolate's global handles to keep shared values
      >   alive in transit during a postMessage
      >
      > Original change's description:
      > > [string] Support shared strings in Value{Serializer,Deserializer}
      > >
      > > When FLAG_shared_string_table is true, postMessaging strings will share
      > > instead of copy.
      > >
      > > Note that not all operations on shared strings are supported, and shared
      > > strings may be slower than non-shared strings for some operations.
      
      Bug: v8:12007
      Change-Id: I70782978ed05558615eca03bafc4c12eba3644ca
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3417189Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Shu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78791}
      fc23bc1d
    • Nico Hartmann's avatar
      Revert "Reland "[string] Support shared strings in Value{Serializer,Deserializer}"" · 199f1c2a
      Nico Hartmann authored
      This reverts commit 5320fe8d.
      
      Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20debug/38175/overview
      
      Original change's description:
      > Reland "[string] Support shared strings in Value{Serializer,Deserializer}"
      >
      > This is a reland of 3cb4039c
      >
      > Changes since revert:
      > - Fix FLAG_stress_scavenge interaction with shared Isolate
      > - Use the shared Isolate's global handles to keep shared values
      >   alive in transit during a postMessage
      >
      > Original change's description:
      > > [string] Support shared strings in Value{Serializer,Deserializer}
      > >
      > > When FLAG_shared_string_table is true, postMessaging strings will share
      > > instead of copy.
      > >
      > > Note that not all operations on shared strings are supported, and shared
      > > strings may be slower than non-shared strings for some operations.
      > >
      > > Bug: v8:12007
      > > Change-Id: I3462128e15410d2568868143571571b3025722c1
      > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277250
      > > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > > Commit-Queue: Shu-yu Guo <syg@chromium.org>
      > > Cr-Commit-Position: refs/heads/main@{#78614}
      >
      > Bug: v8:12007
      > Change-Id: I5d9b99b2dac6f26d5ef046d7aec94f1a1d219419
      > Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3389533
      > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Commit-Queue: Shu-yu Guo <syg@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#78761}
      
      Bug: v8:12007
      Change-Id: Ie8e54b30055324e6592562450b51d5a11e11c9d0
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416232
      Auto-Submit: Nico Hartmann <nicohartmann@chromium.org>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Commit-Queue: Nico Hartmann <nicohartmann@chromium.org>
      Owners-Override: Nico Hartmann <nicohartmann@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78762}
      199f1c2a
    • Shu-yu Guo's avatar
      Reland "[string] Support shared strings in Value{Serializer,Deserializer}" · 5320fe8d
      Shu-yu Guo authored
      This is a reland of 3cb4039c
      
      Changes since revert:
      - Fix FLAG_stress_scavenge interaction with shared Isolate
      - Use the shared Isolate's global handles to keep shared values
        alive in transit during a postMessage
      
      Original change's description:
      > [string] Support shared strings in Value{Serializer,Deserializer}
      >
      > When FLAG_shared_string_table is true, postMessaging strings will share
      > instead of copy.
      >
      > Note that not all operations on shared strings are supported, and shared
      > strings may be slower than non-shared strings for some operations.
      >
      > Bug: v8:12007
      > Change-Id: I3462128e15410d2568868143571571b3025722c1
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277250
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Commit-Queue: Shu-yu Guo <syg@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#78614}
      
      Bug: v8:12007
      Change-Id: I5d9b99b2dac6f26d5ef046d7aec94f1a1d219419
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3389533Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Shu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78761}
      5320fe8d
  12. 25 Jan, 2022 1 commit
  13. 14 Jan, 2022 2 commits
  14. 20 Dec, 2021 1 commit
  15. 08 Dec, 2021 1 commit
  16. 07 Dec, 2021 1 commit
    • Clemens Backes's avatar
      [d8] Make counters fully atomic · 6114d098
      Clemens Backes authored
      Counter updates were already atomic, but reading the counter values was
      not. This lead to data races if one isolate called `quit` while other
      isolates were still running.
      This makes counters fully atomic, and reflects that by making the fields
      {std::atomic<int>}.
      
      R=mlippautz@chromium.org
      
      Bug: v8:12481, v8:12482
      Change-Id: I6fc78ad6461b93c4b3e87bec052b0a67694539e3
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng
      Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3320428Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78279}
      6114d098
  17. 06 Dec, 2021 1 commit
  18. 01 Dec, 2021 1 commit
  19. 05 Nov, 2021 1 commit
    • Camillo Bruni's avatar
      [api] Introduce new HostImportModuleDynamicallyCallback · f0e5e3b2
      Camillo Bruni authored
      The new callback does no longer use ScriptOrModule but rather gets the
      host-defined options and the referrer name as separate arguments.
      
      This brings us one step closer to deprecate ScriptOrModule and putting
      the host-defined options in the script context.
      
      - Add v8::Data::IsFixedArray and cast helpers
      - Deprecate HostImportModuleDynamicallyWithImportAssertionsCallback soon
      - Add Script::Run entry point that explicitly takes host-defined
        options (unused yet)
      
      Bug: chromium:1244145
      Change-Id: I08bc92cfb3b79d840e766fb71b8d91d301f4399c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3263893
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarVictor Gomes <victorgomes@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#77733}
      f0e5e3b2
  20. 04 Nov, 2021 3 commits
    • Camillo Bruni's avatar
      Reland "[d8] Verify host-defined options" · e24bdb6e
      Camillo Bruni authored
      This is a reland of 0446ab7c
      
      Additional fix:
      Manually set the host-defined options on deserialised scripts in d8.
      
      Original change's description:
      > [d8] Verify host-defined options
      >
      > d8 never checked what the actual value of the host-defined options are.
      > We now properly very that the host-defined options is a specific object
      > so we we don't end up accidentally ignoring a wrong options object.
      >
      > Drive-by-fix:
      > - Convert %AbortJS argument to string
      >
      > Bug: chromium:1244145
      > Change-Id: If0ed128d215682bcf066592418420548b06eb6a1
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3259655
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Shu-yu Guo <syg@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#77699}
      
      Bug: chromium:1244145
      Change-Id: I8ddfdba27d84c36862323ab9e1aba14b2ff932a4
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3259539
      Auto-Submit: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
      Commit-Queue: Shu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#77716}
      e24bdb6e
    • Leszek Swirski's avatar
      Revert "[d8] Verify host-defined options" · 0b1824a7
      Leszek Swirski authored
      This reverts commit 0446ab7c.
      
      Reason for revert: Lots of failures https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20debug/37355/overview
      
      Original change's description:
      > [d8] Verify host-defined options
      >
      > d8 never checked what the actual value of the host-defined options are.
      > We now properly very that the host-defined options is a specific object
      > so we we don't end up accidentally ignoring a wrong options object.
      >
      > Drive-by-fix:
      > - Convert %AbortJS argument to string
      >
      > Bug: chromium:1244145
      > Change-Id: If0ed128d215682bcf066592418420548b06eb6a1
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3259655
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Shu-yu Guo <syg@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#77699}
      
      Bug: chromium:1244145
      Change-Id: I267f4bdbd8afce81934f4e813dbe1ec09ebdc1ae
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3259538
      Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      Owners-Override: Leszek Swirski <leszeks@chromium.org>
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/main@{#77705}
      0b1824a7
    • Camillo Bruni's avatar
      [d8] Verify host-defined options · 0446ab7c
      Camillo Bruni authored
      d8 never checked what the actual value of the host-defined options are.
      We now properly very that the host-defined options is a specific object
      so we we don't end up accidentally ignoring a wrong options object.
      
      Drive-by-fix:
      - Convert %AbortJS argument to string
      
      Bug: chromium:1244145
      Change-Id: If0ed128d215682bcf066592418420548b06eb6a1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3259655
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#77699}
      0446ab7c
  21. 11 Oct, 2021 1 commit
  22. 08 Oct, 2021 1 commit
  23. 07 Oct, 2021 1 commit
  24. 26 Aug, 2021 1 commit
  25. 25 Aug, 2021 1 commit
  26. 24 Aug, 2021 1 commit
    • Dan Elphick's avatar
      Reland "[include] Split out v8.h" · ec06bb6c
      Dan Elphick authored
      This is a reland of d1b27019
      
      Fixes include:
      Adding missing file to bazel build
      Forward-declaring classing before friend-classing them to fix win/gcc
      Add missing v8-isolate.h include for vtune builds
      
      Original change's description:
      > [include] Split out v8.h
      >
      > This moves every single class/function out of include/v8.h into a
      > separate header in include/, which v8.h then includes so that
      > externally nothing appears to have changed.
      >
      > Every include of v8.h from inside v8 has been changed to a more
      > fine-grained include.
      >
      > Previously inline functions defined at the bottom of v8.h would call
      > private non-inline functions in the V8 class. Since that class is now
      > in v8-initialization.h and is rarely included (as that would create
      > dependency cycles), this is not possible and so those methods have been
      > moved out of the V8 class into the namespace v8::api_internal.
      >
      > None of the previous files in include/ now #include v8.h, which means
      > if embedders were relying on this transitive dependency then it will
      > give compile failures.
      >
      > v8-inspector.h does depend on v8-scripts.h for the time being to ensure
      > that Chrome continue to compile but that change will be reverted once
      > those transitive #includes in chrome are changed to include it directly.
      >
      > Full design:
      > https://docs.google.com/document/d/1rTD--I8hCAr-Rho1WTumZzFKaDpEp0IJ8ejZtk4nJdA/edit?usp=sharing
      >
      > Bug: v8:11965
      > Change-Id: I53b84b29581632710edc80eb11f819c2097a2877
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3097448
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Dan Elphick <delphick@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#76424}
      
      Cq-Include-Trybots: luci.v8.try:v8_linux_vtunejit
      Bug: v8:11965
      Change-Id: I99f5d3a73bf8fe25b650adfaf9567dc4e44a09e6
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3113629Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#76460}
      ec06bb6c
  27. 23 Aug, 2021 2 commits
    • Dan Elphick's avatar
      Revert "[include] Split out v8.h" · 44fe02ce
      Dan Elphick authored
      This reverts commit d1b27019.
      
      Reason for revert: Broke vtune build, tsan build and possibly others
      
      Original change's description:
      > [include] Split out v8.h
      >
      > This moves every single class/function out of include/v8.h into a
      > separate header in include/, which v8.h then includes so that
      > externally nothing appears to have changed.
      >
      > Every include of v8.h from inside v8 has been changed to a more
      > fine-grained include.
      >
      > Previously inline functions defined at the bottom of v8.h would call
      > private non-inline functions in the V8 class. Since that class is now
      > in v8-initialization.h and is rarely included (as that would create
      > dependency cycles), this is not possible and so those methods have been
      > moved out of the V8 class into the namespace v8::api_internal.
      >
      > None of the previous files in include/ now #include v8.h, which means
      > if embedders were relying on this transitive dependency then it will
      > give compile failures.
      >
      > v8-inspector.h does depend on v8-scripts.h for the time being to ensure
      > that Chrome continue to compile but that change will be reverted once
      > those transitive #includes in chrome are changed to include it directly.
      >
      > Full design:
      > https://docs.google.com/document/d/1rTD--I8hCAr-Rho1WTumZzFKaDpEp0IJ8ejZtk4nJdA/edit?usp=sharing
      >
      > Bug: v8:11965
      > Change-Id: I53b84b29581632710edc80eb11f819c2097a2877
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3097448
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Dan Elphick <delphick@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#76424}
      
      Bug: v8:11965
      Change-Id: Id57313ae992e720c8b19abc975cd69729e1344aa
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3113627
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Owners-Override: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#76428}
      44fe02ce
    • Dan Elphick's avatar
      [include] Split out v8.h · d1b27019
      Dan Elphick authored
      This moves every single class/function out of include/v8.h into a
      separate header in include/, which v8.h then includes so that
      externally nothing appears to have changed.
      
      Every include of v8.h from inside v8 has been changed to a more
      fine-grained include.
      
      Previously inline functions defined at the bottom of v8.h would call
      private non-inline functions in the V8 class. Since that class is now
      in v8-initialization.h and is rarely included (as that would create
      dependency cycles), this is not possible and so those methods have been
      moved out of the V8 class into the namespace v8::api_internal.
      
      None of the previous files in include/ now #include v8.h, which means
      if embedders were relying on this transitive dependency then it will
      give compile failures.
      
      v8-inspector.h does depend on v8-scripts.h for the time being to ensure
      that Chrome continue to compile but that change will be reverted once
      those transitive #includes in chrome are changed to include it directly.
      
      Full design:
      https://docs.google.com/document/d/1rTD--I8hCAr-Rho1WTumZzFKaDpEp0IJ8ejZtk4nJdA/edit?usp=sharing
      
      Bug: v8:11965
      Change-Id: I53b84b29581632710edc80eb11f819c2097a2877
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3097448Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#76424}
      d1b27019
  28. 19 Aug, 2021 1 commit
  29. 30 Jun, 2021 1 commit
  30. 22 Jun, 2021 1 commit
  31. 08 Jun, 2021 1 commit
  32. 04 Jun, 2021 1 commit
  33. 03 Jun, 2021 1 commit
  34. 02 Jun, 2021 1 commit
    • Camillo Bruni's avatar
      Reland "[mjsunit][tools][d8] Full roundtrip tickprocessor test" · 99bfa28b
      Camillo Bruni authored
      This is a reland of ed7e4554:
      - fixing platform names for tickprocessor
      - UnixCppEntriesProvider => LinuxCppEntriesProvider
      - MacCppEntriesProvider => MacOSCppEntriesProvider
      
      Original change's description:
      > [mjsunit][tools][d8] Full roundtrip tickprocessor test
      >
      > - Add os.d8Path property
      > - Add os.name property
      > - Change tickprocssor test to use command line arguments for testing
      >   various configurations
      > - Change tickprocessor test to create a temporary v8.log and read it
      >   back in on linux only
      > - Rearrange code in tickprocessor.mjs to allow instantiating the
      >   CppEntriesProvider directly
      > - Drop complete symbol-list for tickprocessor-test-large.log for better
      >   code searching in V8
      >
      > Change-Id: Ib56dd0a1ba5377282c84c4de6f17e2fd69ee8123
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2929120
      > Reviewed-by: Patrick Thier <pthier@chromium.org>
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#74892}
      
      Change-Id: I5e121ba11f407af50108a2712d27c32867a22eb0
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2929382Reviewed-by: 's avatarPatrick Thier <pthier@chromium.org>
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#74902}
      99bfa28b