https://crbug.com/99679  was claimed fixed. Is this something different?

Yes, I think this issue is something different, because this issue compares two different architectures (i.e. x64 versus arm64) and not different compilers on one architecture.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/f3b5f70cd2c161124a1622b3bcdcde1efa859262 ([foozzie] Add more architectures for correctness comparisons).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 48714:48715.

Detailed report: https://clusterfuzz.com/testcase?key=5497713637720064

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:arm64,ignition
  sources: 59c
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=43152:43153
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48714:48715

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5497713637720064

See https://github.com/google/clusterfuzz-tools for more information.

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

 I had a look at the test case and the output. Looks like a rounding difference (perhaps even a floating-point printing difference) in Math.pow between x64 and arm64. Given that the precision of Math.pow is not specified and the rounding difference appears to be at most one bit in this case, gonna close this as WontFix.

Assigning to me to mock this out better or mark as duplicate of the known rounding error bug.