[compiler] Gracefully handle an unsupported situation

GeorgNeis · V8 LUCI CQ · commit 9a607043cb31 · 2021-09-09T05:28:02.000Z
... by skipping the optimization instead of CHECK-failing. Bug: v8:12188 Change-Id: I6709bf1c55506f3d12886efbfbb9934788cd02ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3148132 Auto-Submit: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#76741}
diff --git a/src/objects/lookup.cc b/src/objects/lookup.cc
@@ -1527,8 +1527,8 @@ base::Optional<PropertyCell> ConcurrentLookupIterator::TryGetPropertyCell(
   DisallowGarbageCollection no_gc;
 
   Map holder_map = holder->map();
-  CHECK(!holder_map.is_access_check_needed());
-  CHECK(!holder_map.has_named_interceptor());
+  if (holder_map.is_access_check_needed()) return {};
+  if (holder_map.has_named_interceptor()) return {};
 
   GlobalDictionary dict = holder->global_dictionary(kAcquireLoad);
   base::Optional<PropertyCell> cell =
