On Fri Nov 3 13:11:39 2023 +0000, Giovanni Mascellani wrote:
I'm not sure this is appropriate. This is the SPIR-V backend, and it should work independently of where the VSIR code it processes was generated. If DXIL confuses signed and unsigned data and VSIR does not, this mismatch should be resolved in the DXIL frontend, not here.
It doesn't confuse signed and unsigned exactly. It always uses unsigned but performs signed ops where necessary. This avoids signed/unsigned bitcasting. Fortunately `SPIR-V` is flexible and allows signed ops on unsigned values. Making VSIR require strict signedness would greatly complicate matters.