There is currently no need to make a special case for 16-bit values, since the SPIR-V backend currently confuses them with 32-bit values. The generated VSIR code is not correct, but that will have to be handled at a different level.