[Perf] Linux/x64: 1 Improvement on 1/23/2026 12:19:42 PM +00:00

### Run Information

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

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

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

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

| 11.70 ns | 10.08 ns | 0.86 | 0.18 | False | | |

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

### System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives<Single>.BitwiseAnd_Vector(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 src/benchmarks/micro/libraries/System.Numerics.Tensors/Perf_NumberTensorPrimitives.cs lines 64-65 and the linked performance report. Run the provided benchmarks_ci.py command, then compare the Linux/x64 BitwiseAnd_Vector result with the baseline to determine whether the reported improvement needs follow-up. Done should include a confirmed explanation or a reproducible correction, but the issue does not specify a requested code change.

Written by the indexing model from the issue text.