On Tue Oct 31 13:15:09 2023 +0000, Henri Verbeet wrote:
While the general concept seems fine and useful, it's not immediately clear to me that this particular approach is a significant improvement over using a small script to launch vkd3d-compiler?
Well, you can see that program as a small script that launches vkd3d-compiler, except that all executions happen in the same process! :-)
I see a few small advantages to have everything happening in the same process: * There is some time save because you don't have to create and teardown the process each time. * In particular, it's easier to have cleaner measurements, because you don't have to exclude the time used for creating and tearing down the process. * In the future one might want to gather statistics about shaders, for example to see which features are more in use, to direct development. This is easier to do in a single process rather than serializing and parsing the statistics state every time.
I'll admit none of these points is really strong, but on the other hand maintaining that program doesn't look complicated either.