I'm not sold on using a single VKD3DSPR_LABEL register to hold two targets. Is there a specific issue this is addressing, or is this simply an attempt to reduce the number of parameters to the instruction?
Agreed. In general I don't think we need to make an internal representation as compact as possible. It's better to have it more uniform and understandable. This might also apply to PHI nodes in !491.