SPIR-V is higher level to avoid platform-specific optimizations that
are sometimes in DX bytecode, and is also more portable than GLSL.
However, SPIR-V could be offline optimized (as tools become more
available) if the ISV was sure it was the right thing to do for the
target set of platforms.|
Do we have data that the size problem is real? The discussion seemed concerned with compile-time performance (while staying secure) up to this point, which should only be improved by SPIR-V. We are looking at improving tools to that fix the size of SPIR-V, so data there will be useful. SPIR-V itself could be smaller, but it was decided that portability and simplicity were more important design goals. Data to revisit that is also interesting, as SPIR-V has room for a different schema that would be smaller (only makes sense for non-compression tool chains).
On 11/14/2016 12:21 PM, Corentin Wallez wrote: