================
@@ -5755,28 +5761,71 @@ static MachineBasicBlock *lowerWaveReduce(MachineInstr
&MI,
break;
}
case AMDGPU::V_ADD_F32_e64:
+ case AMDGPU::V_ADD_F64_e64:
+ case AMDGPU::V_ADD_F64_e64_gfx12:
case AMDGPU::V_SUB_F32_e64: {
- Register ActiveLanesVreg =
- MRI.createVirtualRegister(&AMDGPU::VGPR_32RegClass);
- Register DstVreg = MRI.createVirtualRegister(&AMDGPU::VGPR_32RegClass);
+ bool is32BitOpc = is32bitWaveReduceOperation(Opc);
+ const TargetRegisterClass *VregRC =
+ is32BitOpc ? &AMDGPU::VGPR_32RegClass : TRI->getVGPR64Class();
----------------
easyonaadit wrote:
Yupp got it,
Completely unrelated, but while submitting a change on a down-stack PR,
graphite also force pushes all the up-stack PRs as well, and it leads to a
really messy commit history on github. Lot's of force pushes. I tried to push a
commit using pure git commands, but that seemed to make things worse, it
auto-tagged a lot of reviewers. Is there any trick to make graphite only submit
to one PR, and not force push the up-stack PRs?
https://github.com/llvm/llvm-project/pull/170812
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
