Regression range points towards 7a6f294ffe8e9cc98e266238ec5cd0aa74524c4a. Seems to specific to MIPS.

ClusterFuzz has detected this issue as fixed in range 41595:41596.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5634759536672768

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_mipsel_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !src1.is(src2) in macro-assembler-mips.cc
  
Regressed: V8: r41507:41508
Fixed: V8: r41595:41596

Minimized Testcase (0.11 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv97uDKfw9jTRheMqqXcF1HAMpIqO13GZDI-_NYMCROEV-NPWHrY6VaQiapdBeCp1XzUmmk1ZPuKHUt8BP8OJJZ-Kk74QPbSnhawbKKBl1JtXVUye7IrnHqGtxGx6KZj22DXejbTUvsLcz-xl2Dn2QV7DZMwJlA?testcase_id=5634759536672768
var __v_23 = {};
function __f_21() {
 Math.min(__v_23, __v_23);
}
%OptimizeFunctionOnNextCall(__f_21);
__f_21();


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5634759536672768 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

The problem is fixed with following CL: 
https://chromium.googlesource.com/v8/v8/+/e8f5adbed22c59a7df1530f4979768e6ebcda7c6