diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2025-09-03 01:19:01 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-03 01:19:01 +0900 |
| commit | bb54be585370cc281e60fb6973062004f200c9d3 (patch) | |
| tree | 6c605308cc1391888bddcd3aa3ff9b280fe665d2 /lldb/test/API/python_api | |
| parent | e3e1652d1875c23c794b17250d5fee6a7b076500 (diff) | |
AMDGPU: Fix DPP combiner using isOperandLegal on incomplete inst (#155595)
It is not safe to use isOperandLegal on an instruction that does
not have a complete set of operands. Unforunately the APIs are
not set up in a convenient way to speculatively check if an instruction
will be legal in a hypothetical instruction. Build all the operands
and then verify they are legal after. This is clumsy, we should have
a more direct check for will these operands give a legal instruction.
This seems to fix a missed optimization in the gfx11 test. The
fold was firing for gfx1150, but not gfx1100. Both should support
vop3 literals so I'm not sure why it wasn't working before.
Diffstat (limited to 'lldb/test/API/python_api')
0 files changed, 0 insertions, 0 deletions