[Perf] Windows/arm64: 2 Regressions on 9/3/2026 2:29:33 PM +00:00

### Run Information

Name | Value
-- | --
Architecture | arm64
OS | Windows 10.0.22621
Queue | Pixel
Baseline | [ef3efe5e020e412e4f6453781d59443e975010a4](https://github.com/dotnet/runtime/commit/ef3efe5e020e412e4f6453781d59443e975010a4)
Compare | [a56ab6eb22016f87d149ab6709dee133935372d3](https://github.com/dotnet/runtime/commit/a56ab6eb22016f87d149ab6709dee133935372d3)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ef3efe5e020e412e4f6453781d59443e975010a4...a56ab6eb22016f87d149ab6709dee133935372d3)
Configs | CodeGenType:R2R, CompilationMode:tiered, LinkingType:dynamic, 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\META-INF\ANDROIDD.RSA]()
• [ADX - Test Multi Config Graph]()

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

![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 with the reported SOD - Android HelloWorld Extracted Size benchmark and reproduce it using performance/scripts/benchmarks_ci.py with the command in the Repro section. Compare the baseline and test commits and review the linked test report, graphs, and profiling or benchmarking workflow docs. Done means the two reported regressions are explained and the appropriate runtime or benchmark follow-up is identified.

Written by the indexing model from the issue text.