GFX10 deprecates v_mul_lo_i32 instruction, so choose u32 form for
all targets.
Details
Details
- Reviewers
kzhuravl msearles - Commits
- rZORG3984f37ed974: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
rZORG1293d5c1b532: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
rG3984f37ed974: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
rG1293d5c1b532: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
rG971cb8b633b0: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
rL360094: [AMDGPU] gfx1010: prefer V_MUL_LO_U32 over V_MUL_LO_I32
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
I believe the goal is to generally use the u32 suffix for arithmetic instructions where the signedness doesn't matter, but the ISA has generally been inconsistent about that and the i32 vs. u32 confusion here is simply because they simultaneously (1) changed some encodings around and (2) changed the canonical mnemonic of the instruction. So the _i32 and _u32 variants are really the same instruction semantically.
(The sign does matter for mul_hi)