On Wed Oct 25 14:23:55 2023 +0000, Giovanni Mascellani wrote:
But yep, maybe for consistency even compile-only runs should have
their ops defined, even if they are mostly empty functions or NULL function pointers. I will do that. Yeah, I'd rather have a "null executor" to abstract compilation only, rather than have another flag.
Well, after trying to implement that, I think I prefer the check_syntax flag now, because there are many shader runner ops that must be either all defined or all NULL to make sense (specially all those required by parse_test_directive(), and the create_resource() and destroy_resource() pairs), unless we add a lot of checks or a lot of blank functions, which I think would be better if we do it in a separate `shader_runner_only_compilation.c` file.