There's no reason to ever load into the special registers
in the superclass SReg_64. This helps avoid the verifier
error "Expected a SGPR_64 register, but got a SReg_64 register"
because SGPR_64 is not a superclass of SReg_64 when trying
to use a loaded kernel argument register in some cases.
Details
Details
- Reviewers
- None
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Actually I think this will just hide a more general problem since lots of places use SReg_64 destinations