Bug 1886849: Remove MObjectKeysLength::computeRange r=jandem, a=dsmith

Differential Revision: https://phabricator.services.mozilla.com/D205375
i3roly · Mar 21, 2024 · bdf3090 · bdf3090
1 parent f4b3793
commit bdf3090
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 8 deletions.
diff --git a/js/src/jit/MIROps.yaml b/js/src/jit/MIROps.yaml
@@ -1733,7 +1733,6 @@
   movable: false
   congruent_to: if_operands_equal
   alias_set: custom
-  compute_range: custom
   clone: true
 
 - name: LoadUnboxedScalar

diff --git a/js/src/jit/RangeAnalysis.cpp b/js/src/jit/RangeAnalysis.cpp
@@ -1821,13 +1821,6 @@ void MResizableDataViewByteLength::computeRange(TempAllocator& alloc) {
   }
 }
 
-void MObjectKeysLength::computeRange(TempAllocator& alloc) {
-  // Object.keys(..) returns an array, but this array is bounded by the number
-  // of slots / elements that can be encoded in a single object.
-  MOZ_ASSERT(type() == MIRType::Int32);
-  setRange(Range::NewUInt32Range(alloc, 0, NativeObject::MAX_SLOTS_COUNT));
-}
-
 void MTypedArrayElementSize::computeRange(TempAllocator& alloc) {
   constexpr auto MaxTypedArraySize = sizeof(double);