[compiler] Remove --turbo-...-ispendingallocation flag

No longer needed now that the predicate is fixed.

Bug: v8:7790,v8:11779
Change-Id: If585c3692aed77659b53f670182129988ba93130
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2996193
Auto-Submit: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Reviewed-by: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#75486}

src/compiler/heap-refs.cc

@@ -2809,17 +2809,12 @@ ObjectData* JSHeapBroker::TryGetOrCreateData(Handle<Object> object,
 
   const bool crash_on_error = (flags & kCrashOnError) != 0;
 
-  // TODO(jgruber): Remove this flag check (and the flag) once TSAN failures
-  // are fixed.
-  // See also: crbug.com/v8/11779
-  if (FLAG_turbo_concurrent_inlining_check_ispendingallocation) {
   if ((flags & kAssumeMemoryFence) == 0 &&
       ObjectMayBeUninitialized(HeapObject::cast(*object))) {
     TRACE_BROKER_MISSING(this, "Object may be uninitialized " << *object);
     CHECK_WITH_MSG(!crash_on_error, "Ref construction failed");
     return nullptr;
   }
-  }
 
   if (IsReadOnlyHeapObjectForCompiler(HeapObject::cast(*object))) {
     entry = refs_->LookupOrInsert(object.address());

src/flags/flag-definitions.h

@@ -711,9 +711,6 @@ DEFINE_WEAK_VALUE_IMPLICATION(stress_concurrent_inlining, interrupt_budget,
 DEFINE_BOOL(
     turbo_concurrent_get_property_access_info, false,
     "concurrently call GetPropertyAccessInfo (only with --concurrent-inlining)")
-DEFINE_BOOL(turbo_concurrent_inlining_check_ispendingallocation, true,
-            "when --concurrent-inlining is enabled, check IsPendingAllocation "
-            "in Ref construction")
 DEFINE_INT(max_serializer_nesting, 25,
            "maximum levels for nesting child serializers")
 DEFINE_WEAK_IMPLICATION(future, concurrent_inlining)