1. 06 Oct, 2020 15 commits
  2. 05 Oct, 2020 25 commits
    • Adam Klein's avatar
      Revert "Reland^3 "[serializer] Allocate during deserialization"" · a10ec2be
      Adam Klein authored
      This reverts commit 3f4e9bbe, along
      with the following dependent changes (reverted to make this a clean revert):
      76ad3ab5 [identity-map] Change resize heuristic
      77cc96aa [identity-map] Cache the calculated Hash
      bee5b996 [serializer] Remove Deserializer::Initialize
      c8f73f22 [serializer] Cache instance type in PostProcessNewObject
      4e7c99ab [identity-map] Remove double-lookups in IdentityMap
      
      Reason for revert: major crash spike on Canary (https://crbug.com/1135027)
      
      Original change's description:
      > Reland^3 "[serializer] Allocate during deserialization"
      >
      > This is a reland of c4a062a9
      > which was a reland of 28a30c57
      > which was a reland of 5d7a29c9
      >
      > Fixes TSAN errors from non-atomic writes in the deserializer. Now all
      > writes are (relaxed) atomic.
      >
      > Original change's description:
      > > Reland^2 "[serializer] Allocate during deserialization"
      > >
      > > This is a reland of 28a30c57
      > > which was a reland of 5d7a29c9
      > >
      > > The crashes were from calling RegisterDeserializerFinished on a null
      > > Isolate pointer, for a deserializer that was never initialised
      > > (specifically, ReadOnlyDeserializer when ROHeap is shared).
      > >
      > > Original change's description:
      > > > Reland "[serializer] Allocate during deserialization"
      > > >
      > > > This is a reland of 5d7a29c9
      > > >
      > > > This reland shuffles around the order of checks in Heap::AllocateRawWith
      > > > to not check the new space addresses until it's known that this is a new
      > > > space allocation. This fixes an UBSan failure during read-only space
      > > > deserialization, which happens before the new space is initialized.
      > > >
      > > > It also fixes some issues discovered by --stress-snapshot, around
      > > > serializing ThinStrings (which are now elided as part of serialization),
      > > > handle counts (I bumped the maximum handle count in that check), and
      > > > clearing map transitions (the map backpointer field needed a Smi
      > > > uninitialized value check).
      > > >
      > > > Original change's description:
      > > > > [serializer] Allocate during deserialization
      > > > >
      > > > > This patch removes the concept of reservations and a specialized
      > > > > deserializer allocator, and instead makes the deserializer allocate
      > > > > directly with the Heap's Allocate method.
      > > > >
      > > > > The major consequence of this is that the GC can now run during
      > > > > deserialization, which means that:
      > > > >
      > > > >   a) Deserialized objects are visible to the GC, and
      > > > >   b) Objects that the deserializer/deserialized objects point to can
      > > > >      move.
      > > > >
      > > > > Point a) is mostly not a problem due to previous work in making
      > > > > deserialized objects "GC valid", i.e. making sure that they have a valid
      > > > > size before any subsequent allocation/safepoint. We now additionally
      > > > > have to initialize the allocated space with a valid tagged value -- this
      > > > > is a magic Smi value to keep "uninitialized" checks simple.
      > > > >
      > > > > Point b) is solved by Handlifying the deserializer. This involves
      > > > > changing any vectors of objects into vectors of Handles, and any object
      > > > > keyed map into an IdentityMap (we can't use Handles as keys because
      > > > > the object's address is no longer a stable hash).
      > > > >
      > > > > Back-references can no longer be direct chunk offsets, so instead the
      > > > > deserializer stores a Handle to each deserialized object, and the
      > > > > backreference is an index into this handle array. This encoding could
      > > > > be optimized in the future with e.g. a second pass over the serialized
      > > > > array which emits a different bytecode for objects that are and aren't
      > > > > back-referenced.
      > > > >
      > > > > Additionally, the slot-walk over objects to initialize them can no
      > > > > longer use absolute slot offsets, as again an object may move and its
      > > > > slot address would become invalid. Now, slots are walked as relative
      > > > > offsets to a Handle to the object, or as absolute slots for the case of
      > > > > root pointers. A concept of "slot accessor" is introduced to share the
      > > > > code between these two modes, and writing the slot (including write
      > > > > barriers) is abstracted into this accessor.
      > > > >
      > > > > Finally, the Code body walk is modified to deserialize all objects
      > > > > referred to by RelocInfos before doing the RelocInfo walk itself. This
      > > > > is because RelocInfoIterator uses raw pointers, so we cannot allocate
      > > > > during a RelocInfo walk.
      > > > >
      > > > > As a drive-by, the VariableRawData bytecode is tweaked to use tagged
      > > > > size rather than byte size -- the size is expected to be tagged-aligned
      > > > > anyway, so now we get an extra few bits in the size encoding.
      > > > >
      > > > > Bug: chromium:1075999
      > > > > Change-Id: I672c42f553f2669888cc5e35d692c1b8ece1845e
      > > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404451
      > > > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      > > > > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > > > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > > > > Cr-Commit-Position: refs/heads/master@{#70229}
      > > >
      > > > Bug: chromium:1075999
      > > > Change-Id: Ibc77cc48b3440b4a28b09746cfc47e50c340ce54
      > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2440828
      > > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      > > > Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      > > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > > > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > > > Cr-Commit-Position: refs/heads/master@{#70267}
      > >
      > > Tbr: jgruber@chromium.org,ulan@chromium.org
      > > Bug: chromium:1075999
      > > Change-Id: Iaa8dc54895866ada0e34a7c9e8fff9ae1cb13f2d
      > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2444991
      > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#70279}
      >
      > Tbr: jgruber@chromium.org,ulan@chromium.org
      > Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng,v8_linux64_tsan_no_cm_rel_ng,v8_linux64_tsan_isolates_rel_ng
      > Bug: chromium:1075999
      > Change-Id: I0b9b11644aebc4cc8b07c62a0f765b24e4d73d89
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2445872
      > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      > Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#70288}
      
      TBR=ulan@chromium.org,jgruber@chromium.org,leszeks@chromium.org,dinfuehr@chromium.org
      
      Bug: chromium:1075999, chromium:1135027
      Change-Id: I5d0d9e49c0302d94ff7291834f5f18e7a0839eb7
      Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng,v8_linux64_tsan_no_cm_rel_ng,v8_linux64_tsan_isolates_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2451030Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Commit-Queue: Adam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70328}
      a10ec2be
    • Milad Fa's avatar
      s390: [was-simd] Fix Vector pack and unpack behaviour. · f29078a8
      Milad Fa authored
      Due to the lane numbering difference between Intel and IBM machines,
      we need to switch the input registers when doing a vector pack.
      
      Change-Id: I40e1fdae308e5dcd67aafab2abf099d4be0bb1a2
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2450832Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
      Commit-Queue: Milad Fa <mfarazma@redhat.com>
      Cr-Commit-Position: refs/heads/master@{#70327}
      f29078a8
    • Shu-yu Guo's avatar
      Revert "[heap] String::MakeThin can get away without NotifyObjectLayoutChange" · 9edcb196
      Shu-yu Guo authored
      This reverts commit 6e621f84.
      
      Reason for revert: Suspicion of GC stress failures like https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20gc%20stress/30260
      
      Original change's description:
      > [heap] String::MakeThin can get away without NotifyObjectLayoutChange
      >
      > String::MakeThin doesn't need to invoke NotifyObjectLayoutChange because
      > ThinString will only introduce tagged values and hence will not
      > overwrite recorded slots with untagged values.
      >
      > Bug: v8:10315
      > Change-Id: Iaff9c06cef763462eb57bf3debc5183ae8db6fa0
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448792
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#70321}
      
      TBR=ulan@chromium.org,leszeks@chromium.org,dinfuehr@chromium.org
      
      Change-Id: I11c12e25702eb816cf616593d817a6ee3f691188
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:10315
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2451029Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
      Commit-Queue: Shu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70326}
      9edcb196
    • Seth Brenith's avatar
      [torque] Generate shorter code for indexed field accesses · 73a8eded
      Seth Brenith authored
      Currently, when accessing a field that doesn't have a constant offset,
      Torque emits code to compute each preceding indexed field's length and
      add them all together. This works, but such code can get super long if a
      class has many indexed fields, and especially if the length expressions
      of some indexed fields refer to other indexed fields. We'd like the
      output of the new C++ backend to be short enough to go in inline headers
      which will be included in many compilation units.
      
      This change attempts to reorganize the code so that the computation of
      each length expression can only be emitted exactly once. This only
      shortens the generated C++ code; the resulting TurboFan output should be
      identical. There are two main parts:
      1. For each indexed field, we already generate a macro that can get a
         Slice referring to that field. Update these macros to not use the dot
         operator on that field. Using the dot operator on the predecessor
         field is allowed.
      2. Update the dot operator for indexed fields to emit a call to the
         macro from step 1.
      
      This sort of reverses the dependency added by the previous change
      https://crrev.com/c/2429566 : rather than the slice macros depending on
      the dot operator, this change makes the dot operator depend on the slice
      macros.
      
      The overall torque_generated directory shrinks by under 1% with this
      change, but the runtime_macros.cc file (which should eventually become
      inline headers) shrinks by 24%. More to the point, this change keeps
      runtime_macros.cc from ballooning out of control when we add a
      work-in-progress Torque definition for ScopeInfo
      ( https://crrev.com/c/2357758 ).
      
      Bug: v8:7793
      Change-Id: I989dda9c3666f1a49281fef03acb35baebb5b63a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2432070Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#70325}
      73a8eded
    • Leszek Swirski's avatar
      [identity-map] Change resize heuristic · 76ad3ab5
      Leszek Swirski authored
      Change the resizing behaviour on insert to match that of the hash map
      in base. Specifically, resize when hitting 80% occupancy.
      
      Locally, I measure a ~6% improvement in serialization time from this
      change.
      
      Change-Id: I3fe84de39b2337859fe75fa6b3848198b82071ae
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448798
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70324}
      76ad3ab5
    • Maya Lekova's avatar
      [turbofan] Make OSR and stack slots compatible · 95bb97bc
      Maya Lekova authored
      Bug: chromium:1130844, v8:10973
      Change-Id: I912f2cf6cedaf22dd50d456622880ea266b65dcd
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2445509
      Commit-Queue: Maya Lekova <mslekova@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70323}
      95bb97bc
    • Georg Neis's avatar
      Rename SYNCHRONIZED_ACCESSORS* to RELEASE_ACQUIRE_ACCESSORS* · e2b6fa84
      Georg Neis authored
      ... so that they match the corresponding DECL_* macros.
      
      Change-Id: Idb26901eeb1219945a1e701dd7c28a58ce978bf9
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2449977Reviewed-by: 's avatarSantiago Aboy Solanes <solanes@chromium.org>
      Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
      Auto-Submit: Georg Neis <neis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70322}
      e2b6fa84
    • Dominik Inführ's avatar
      [heap] String::MakeThin can get away without NotifyObjectLayoutChange · 6e621f84
      Dominik Inführ authored
      String::MakeThin doesn't need to invoke NotifyObjectLayoutChange because
      ThinString will only introduce tagged values and hence will not
      overwrite recorded slots with untagged values.
      
      Bug: v8:10315
      Change-Id: Iaff9c06cef763462eb57bf3debc5183ae8db6fa0
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448792Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70321}
      6e621f84
    • Clemens Backes's avatar
      [wasm][fuzzer] Fix data race when setting flags · a024ea4b
      Clemens Backes authored
      Fuzzers are executed in their own process, so instead of resetting flags
      after execution, we can just keep the flag values.
      This CL introduces a shared function to enable all staged features,
      without ever resetting the value. This fixes a data race.
      
      R=ahaas@chromium.org
      
      Bug: v8:10979
      Change-Id: I82ea35b887841850edd8b394a3644cf8df1e3bf8
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2449969
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70320}
      a024ea4b
    • Leszek Swirski's avatar
      [identity-map] Cache the calculated Hash · 77cc96aa
      Leszek Swirski authored
      In IdentityMap, explicitly pass the key's hash so that it can be cached
      between Lookup and Insert.
      
      Change-Id: Ib8a2d96cc399ae025f54c61c129dd4cd18d86c7e
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448795
      Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70319}
      77cc96aa
    • Manos Koukoutos's avatar
      [wasm-gc][bug] Fix signature canonicalization · 4d9d8518
      Manos Koukoutos authored
      We used not to emit canonical indexes for arrays and structs into
      WasmModule::signature_ids, which resulted in signature_ids not referring
      to the correct type indices in a WasmModule.
      
      Changes:
      - Rename signature_ids to canonical_type_ids.
      - Emit trivial canonical type ids for structs and arrays.
      - Add a test to catch the existing bug.
      - Improve DCHECKs for module type accessors.
      
      Bug: v8:7748
      Change-Id: I67ad58865e35b459b21db12557564b652035db75
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2444989
      Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70318}
      4d9d8518
    • Ulan Degenbaev's avatar
      [heap] Convert WeakObjects to heap::base::Worklist · 969cdfe6
      Ulan Degenbaev authored
      This splits WeakObjects into explicit global and local worklists.
      The latter are defined in WeakObjects::Local and are thread-local.
      
      The main thread local worklist is stored in
      MarkCompactCollector::local_weak_objects and exists during marking
      similar to local_marking_worklists. Concurrent markers create their
      own local worklists that are published at the end.
      
      Change-Id: I093fdc580b4609ce83455b860b90a5099085beac
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2440607
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70317}
      969cdfe6
    • Ulan Degenbaev's avatar
      [test] Add ManualGCScope to test-spaces/SizeOfInitialHeap · defe1a0f
      Ulan Degenbaev authored
      The test does not expect GC to happen while it is running
      
      Bug: v8:10988
      Change-Id: Idcd30bde4ae1a7c3386a5d8c4c46e46e839e0fe9
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2449971Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70316}
      defe1a0f
    • Philip Pfaffe's avatar
      Expose a proxy object to evaluateOnCallFrame for WebAssembly · ae3f94bd
      Philip Pfaffe authored
      When debugging WebAssembly, calls to evaluateOnCallFrame always return
      undefined. This CL enables evaluateOnCallFrame for WebAssembly and
      creates a proxy object that is injected into the evaluation context.
      
      Bug: chromium:1127914
      Change-Id: I3f5cff3be2c9de45c7b1f3f7ed4fc2e1cc545ac6
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2429265
      Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
      Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70315}
      ae3f94bd
    • Santiago Aboy Solanes's avatar
      [cleanup] Remove unused context parameters · a5024f9b
      Santiago Aboy Solanes authored
      These three wasm methods do not use the context, but were passed one:
       * WasmInt32ToHeapNumber
       * WasmFloat32ToNumber
       * WasmFloat64ToNumber
      
      Bug: v8:6949, v8:10933
      Change-Id: I55e4264f7e06f3fb8338df77d12132c938acfcff
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2445934Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70314}
      a5024f9b
    • Seth Brenith's avatar
      [torque] Add C++ backend for Torque compiler · c7c5d50d
      Seth Brenith authored
      This change adds a new code generator, which supports a subset of the
      instructions supported by the existing CSAGenerator, and instead of
      generating CSA it generates runtime C++ code. The new generator is used
      to generate a set of Torque macros that return slices to indexed fields.
      These new macros should be sufficient to eventually support
      Torque-generated field accessors, BodyDescriptors, verifier functions,
      and postmortem field inspection in debug_helper.
      
      Bug: v8:7793
      Change-Id: Ife2d25cfd55a08238c625a8b04aca3ff2a0f4c63
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2429566Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#70313}
      c7c5d50d
    • Leszek Swirski's avatar
      [intl] Fix timezone bug in test · b90717df
      Leszek Swirski authored
      If we're testing printing in UTC timezone, then we have to be careful to
      also input the date in UTC, else local timezone will affect the test.
      
      Fixed: chromium:1135116
      Change-Id: I49981c263e7b1fa1492b4644c5d4846fd94e5613
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448793
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarSantiago Aboy Solanes <solanes@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70312}
      b90717df
    • Manos Koukoutos's avatar
      [wasm-gc][bug] call_indirect should check for null table entries · cdb3da7f
      Manos Koukoutos authored
      This was not happening when there was no need to typecheck the entry.
      
      Additional changes:
      - Add tests with null table entries for typed and untyped function
        tables.
      - Allow AddIndirectFunctionTable in wasm-run-utils to specify table
        type.
      - Add possibility to define tables in test-gc.cc.
      - Merge trapTableOutOfBounds with trapInvalidFunc.
      - Use trapTableOutOfBounds in call_indirect as appropriate.
      - Fix emission of table types in wasm-module-builder.cc.
      
      Bug: v8:9495
      Change-Id: I4a857ff4378e5a87dc0646d94b4c75635a43c55b
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2442622Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70311}
      cdb3da7f
    • Leszek Swirski's avatar
      [serializer] Remove Deserializer::Initialize · bee5b996
      Leszek Swirski authored
      Remove the separate Initialize method from Deserializer, opting instead
      to pass around SnapshotData where appropriate and pass the isolate
      directly into the Deserializer's constructor.
      
      Change-Id: I0092fadd9c81f14b2ce75145fd81af37c3947c65
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448466
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarDan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70310}
      bee5b996
    • Omer Katz's avatar
      cppgc: Thread safe JSMember · f6bc6b6d
      Omer Katz authored
      Make all writes to JSMember.val_ atomic and atomically check for
      emptiness in Trace.
      
      Bug: chromium:1056170
      Change-Id: Ia7034b9318df081aa61c9b6664903dd4f73402a5
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2431569Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Omer Katz <omerkatz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70309}
      f6bc6b6d
    • Ulan Degenbaev's avatar
      [heap] Refactor marking weak object worklists · ff61743f
      Ulan Degenbaev authored
      This CL extracts weak object worklist related code into separate files
      and uses a macro to specify all weak object worklists in a generic way.
      
      The motivation of the refactoring is twofold:
      1) We can now enforce that each weak object worklist is updated after
         Scavenge. (Forgetting to define the update function causes a link
         time error.)
      2) The reduced boilerplate will be useful for transitioning to the
         new ::heap::base::Worklist.
      
      Change-Id: Ic80a7ccca010c09370d6525f43d78de24192f8ea
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2442624Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70308}
      ff61743f
    • Santiago Aboy Solanes's avatar
      [csa][cleanup] Partly TNodify SharedArrayBuffer's AssemblerFunction · a50f54c1
      Santiago Aboy Solanes authored
      As a drive-by, rename "sanity check" to "check" in sharedarraybuffer.
      
      Bug: v8:6949, v8:10933
      Change-Id: Ifa2eac381ed309a099b018de4033816ebe3d828d
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2429410
      Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70307}
      a50f54c1
    • Santiago Aboy Solanes's avatar
      [cleanup] Clean up SYNCHRONIZED_ACCESSORS macro naming and its uses · c7c8472d
      Santiago Aboy Solanes authored
      We can use tag dispatching to distinguish between the synchronized and
      non-synchronized accessors. Also eliminated the need of adding explicit
      "synchronized" in the name when using the macros.
      
      As a note, we currently have one case of using both relaxed and
      synchronized accessors (Map::instance_descriptors).
      
      Cleaned up:
       * BytecodeArray::source_position_table
       * Code::code_data_container
       * Code::source_position_table
       * FunctionTemplateInfo::call_code
       * Map::instance_descriptors
       * Map::layout_descriptor
       * SharedFunctionInfo::function_data
      
      Bug: v8:7790
      Change-Id: I5a502f4b2df6addb6c45056e77061271012c7d90
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2424130
      Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70306}
      c7c8472d
    • Benedikt Meurer's avatar
      [wasm][debug] Ignore empty local names. · 215238d3
      Benedikt Meurer authored
      Other WebAssembly tools like wabt and wasmparser ignore empty strings
      for local variable and parameter names, and just generate their own
      names for it. Update V8 to comply with this convention.
      
      Bug: chromium:1134531
      Change-Id: Ic724482d93398feaf6b0797eec5a55f8ca508ca5
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448457Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarKim-Anh Tran <kimanh@chromium.org>
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70305}
      215238d3
    • Sathya Gunasekaran's avatar
      [turboprop] Inline monomorphic map check · 2cf6ee0b
      Sathya Gunasekaran authored
      Instead of loading the map from the feedback vector for monomorphic
      access, this CL directly inlines the expected map constant as a static
      check.
      
      In case this static check fails, we call out to a builtin which performs
      additional dynamic map checks.
      
      There are several dynamic map checks performed by the builtin for various
      cases such as:
      (a) IC is monomorphic with a map that's different from the initial
      static map that we checked, in which case we perform another dynamic
      map check.
      (b) IC is monomorphic but incoming map is a deprecated map in which case
      we call out the runtime to migrate this incoming object to a new map and
      then try to handle it.
      (c) IC has now transitioned to polymorphic in which we use the old
      dynamic polymorphic checks to validate the map and handler.
      
      Bug: v8:10582, v8:9684
      Change-Id: Id87265ed513e4aef87b8e66c826afbf10f50a1d0
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2429034
      Commit-Queue: Sathya Gunasekaran  <gsathya@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarMythri Alle <mythria@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70304}
      2cf6ee0b