[Perf] Windows/arm64: 2 Regressions on 6/21/2026 8:35:09 AM +00:00

### Run Information

Name | Value
-- | --
Architecture | arm64
OS | Windows 10.0.22621
Queue | Pixel
Baseline | [b1ea6ff8a102c76f5f8ffdf55a8a2a7fc40de61b](https://github.com/dotnet/runtime/commit/b1ea6ff8a102c76f5f8ffdf55a8a2a7fc40de61b)
Compare | [e556d5a7e0e7f3682eea7ce544b29c6f6c75a216](https://github.com/dotnet/runtime/commit/e556d5a7e0e7f3682eea7ce544b29c6f6c75a216)
Diff | [Diff](https://github.com/dotnet/runtime/compare/b1ea6ff8a102c76f5f8ffdf55a8a2a7fc40de61b...e556d5a7e0e7f3682eea7ce544b29c6f6c75a216)
Configs | CodeGenType:JIT, CompilationMode:tiered, LinkingType:static, RunKind:android_scenarios, RuntimeType:coreclr

### Regressions in SOD - Android HelloWorld Extracted Size

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

• [SOD - Android HelloWorld Extracted Size - pub\lib\arm64-v8a\libmonodroid.so]()
• [ADX - Test Multi Config Graph]()

• [SOD - Android HelloWorld Extracted Size - Aggregate - .so]()
• [ADX - Test Multi Config Graph]()

![graph]()
[Test Report]()

### Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md

```cmd
git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'SOD - Android HelloWorld Extracted Size*'
```

### SOD - Android HelloWorld Extracted Size

#### ETL Files

#### Histogram

#### JIT Disasms

### Docs

[Profiling workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/profiling-workflow-dotnet-runtime.md)
[Benchmarking workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md)

Start by following the reproduction command in performance/scripts/benchmarks_ci.py with the SOD - Android HelloWorld Extracted Size filter, then compare the baseline and compare commits linked in the run information. Use the profiling and benchmarking workflow documents to investigate the extracted-size regression; done means identifying and correcting the regression and confirming the benchmark no longer reports it.

Written by the indexing model from the issue text.