[Perf] Windows/x86: 1 Improvement on 1/25/2026 5:58:29 PM +00:00

### Run Information

Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [8fafcb3251a3d2ccde36612a2eab47e9ae8ebe2b](https://github.com/dotnet/runtime/commit/8fafcb3251a3d2ccde36612a2eab47e9ae8ebe2b)
Compare | [32cae3846c5e91040c870577ecdc0448a6fd7669](https://github.com/dotnet/runtime/commit/32cae3846c5e91040c870577ecdc0448a6fd7669)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8fafcb3251a3d2ccde36612a2eab47e9ae8ebe2b...32cae3846c5e91040c870577ecdc0448a6fd7669)
Configs | CompilationMode:tiered, RunKind:micro

### Improvements in System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives<Double>

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

• [Negate - Duration of single invocation]()
• 📝 - [Benchmark Source]()
• [ADX - Test Multi Config Graph]()

| 20.50 ns | 18.56 ns | 0.91 | 0.28 | False | | |

[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 'System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives*'
```

### System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives<Double>.Negate(BufferLength: 128)

#### 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 benchmark source at performance/src/benchmarks/micro/libraries/System.Numerics.Tensors/Perf_NumberTensorPrimitives.cs#L44-L45 and run the provided benchmarks_ci.py command for the Negate benchmark. Compare the linked baseline and test reports, then use the profiling workflow to determine whether the reported x86 Windows improvement needs follow-up.

Written by the indexing model from the issue text.