Skip to content
ONNX Runtime DirectML Builds

[Kernel] Fix bug in Einsum implementation when a lone operand had a reduction operation #10235

Sign in to view logs

[Kernel] Fix bug in Einsum implementation when a lone operand had a reduction operation

[Kernel] Fix bug in Einsum implementation when a lone operand had a reduction operation #10235

Triggered via pull request February 5, 2026 18:40
@hariharans29hariharans29
synchronize #27225
hari/einsum_fix_1
Status Success
Total duration 2h 46m 45s
Artifacts –

windows_dml.yml

on: pull_request
Windows GPU DML CI Pipeline
1h 30m
Windows GPU DML CI Pipeline
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1234
epilog offset from end of function exceeds 4095
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1227
epilog offset from end of function exceeds 4095
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1220
epilog offset from end of function exceeds 4095
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1213
epilog offset from end of function exceeds 4095
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1206
epilog offset from end of function exceeds 4095
Windows GPU DML CI Pipeline: onnxruntime/core/mlas/lib/amd64/QgemmU8X8KernelAvx2.asm#L1199
epilog offset from end of function exceeds 4095