diff options
| author | Ayush Kumar Gaur <132849148+Ayush3941@users.noreply.github.com> | 2026-02-07 08:25:03 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-02-07 08:25:03 -0500 |
| commit | c3811805369be90f7fdac4c46e6bcc24019748dd (patch) | |
| tree | 6b905dbe2e745fe83de1cda6534fbfcbc8998ea6 /offload/unittests/OffloadAPI/device_code/multiargs.cpp | |
| parent | 9029744432a708b7203e707970dacf2734f3ca21 (diff) | |
| download | llvm-c3811805369be90f7fdac4c46e6bcc24019748dd.zip llvm-c3811805369be90f7fdac4c46e6bcc24019748dd.tar.gz llvm-c3811805369be90f7fdac4c46e6bcc24019748dd.tar.bz2 | |
[mlir][AMDGPU] Avoid verifier crash in DPPOp on vector operand types (#178887)
### whats the problem
mlir-opt could crash while verifying amdgpu.dpp when its operands had
vector
types, such as ARM SME tile vectors produced by arm_sme.get_tile.
The crash occurred during IR verification, before any lowering or passes
ran.
### why it happens
DPPOp::verify() called Type::getIntOrFloatBitWidth() on the operand
type.
When the operand was a VectorType, this hit an assertion because only
scalar
integer and float types have a bitwidth.
### whats the fix
Query the bitwidth on the element type using getElementTypeOrSelf()
instead of
the container type.
Add a regression test to ensure amdgpu.dpp verification no longer
asserts on
vector operand types.
Fixes #178128
Diffstat (limited to 'offload/unittests/OffloadAPI/device_code/multiargs.cpp')
0 files changed, 0 insertions, 0 deletions
