[Perf] Linux/x64: 1 Regression on 8/22/2026 9:15:18 AM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1](https://github.com/dotnet/runtime/commit/f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1)
Compare | [efc7248c8c8a7aa7ad30a58623ee5284ce462a17](https://github.com/dotnet/runtime/commit/efc7248c8c8a7aa7ad30a58623ee5284ce462a17)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1...efc7248c8c8a7aa7ad30a58623ee5284ce462a17)
Configs | CompilationMode:wasm, RunKind:micro

### Regressions in System.Buffers.Binary.Tests.BinaryReadAndWriteTests

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

• [ReadStructFieldByFieldBE - Duration of single invocation]()
• 📝 - [Benchmark Source]()
• [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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Buffers.Binary.Tests.BinaryReadAndWriteTests*'
```

### System.Buffers.Binary.Tests.BinaryReadAndWriteTests.ReadStructFieldByFieldBE

#### 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 benchmark in src/benchmarks/micro/libraries/System.Buffers/BinaryReadAndWriteTests.cs, especially ReadStructFieldByFieldBE, then compare the listed baseline and compare commits. Run the provided benchmarks_ci.py command using the System.Buffers.Binary.Tests.BinaryReadAndWriteTests filter and inspect the linked test report and graph. Done means the regression is explained and the benchmark result is verified against the report.

Written by the indexing model from the issue text.