In the cases where the CMOV (f16) SDNode is used with condition codes
LT, LE, VC or NE, it is successfully selected into a VSEL instruction.
In the remaining cases, however, instruction selection fails since VSEL
does not support other condition codes.
This patch handles such cases by using the single-precision version of
the VMOV instruction.
If this is ending up as a VMOVS, it can actually be HasFPRegs? I guess it shouldn't matter though, if we are not ever selecting the ARMcmov for an fp16.
The itinerary could also be IIC_fpUNA32, but I don't think they will really be used anywhere or make much of a difference.
If HasFPRegs looks like it will cause problems in any way, then HasFPRegs16 would be fine too.