Environment:
- OS: Fedora Linux 44
- GPU and driver version: RADV from Mesa main
- SDK or header version if building from repo: aaeec0b
- Options enabled (synchronization, best practices, etc.): defaults+synchronization
Describe the Issue
I'm not sure if this is an issue with the spec, or the layers, or both, because I can't find an explicit VU for this. I was discussing with a graphics driver dev if it was legal to omit the render pass from the fragment shader library when using graphics pipeline libraries. My idea was that the render pass was mandatory when using classic render passes, and could only be null if using dynamic rendering. However, to verify it I ran an experiment in which I passed the render pass handle to every piece that needs it (pre-rasterization shaders, fragment output) but not to the frag shader lib, and the layers stayed silent.
Expected behavior
I expected the layers to complain, either at frag shader lib creation time, because the render pass is null but no VkPipelineRenderingCreateInfo was being passed (however, I think the spec says this is fine and there are some defaults), or at library link time when putting all the pieces together because of the inconsistency.
Valid Usage ID
N/A
Additional context
N/A
Environment:
Describe the Issue
I'm not sure if this is an issue with the spec, or the layers, or both, because I can't find an explicit VU for this. I was discussing with a graphics driver dev if it was legal to omit the render pass from the fragment shader library when using graphics pipeline libraries. My idea was that the render pass was mandatory when using classic render passes, and could only be null if using dynamic rendering. However, to verify it I ran an experiment in which I passed the render pass handle to every piece that needs it (pre-rasterization shaders, fragment output) but not to the frag shader lib, and the layers stayed silent.
Expected behavior
I expected the layers to complain, either at frag shader lib creation time, because the render pass is null but no VkPipelineRenderingCreateInfo was being passed (however, I think the spec says this is fine and there are some defaults), or at library link time when putting all the pieces together because of the inconsistency.
Valid Usage ID
N/A
Additional context
N/A