Lines Matching defs:module
79 // Helper function to create a shader module identifier from a VkShaderModuleIdentifierEXT structure.
89 // Helper function to obtain the shader module identifier for a VkShaderModule as a return value.
90 ShaderModuleId getShaderModuleIdentifier (const DeviceInterface& vkd, const VkDevice device, const VkShaderModule module)
93 vkd.getShaderModuleIdentifierEXT(device, module, &idExt);
97 // Helper function to obtain the shader module identifier from a VkShaderModuleCreateInfo structure as a return value.
119 // On the actual pipeline in use, will we use module IDs or other data?
167 // Modify a shader module id according to the type of use.
192 case UseModuleCase::ALL_ZEROS: // For this one and below, the module id will have been modified outside.
218 ShaderWrapper* retUsedModule (ShaderWrapper* module, UseModuleCase moduleUse)
221 return (isZeroLen(moduleUse) ? module : &emptyWrapper);
1373 // Check shader module identifiers are constant across different API calls.
1458 return tcu::TestStatus::fail("The same shader module returned different identifiers");
1466 // Helper to create a new device supporting shader module identifiers.
2396 retUsedModule(&compModule, m_params->moduleUseCase)->getModule(), // VkShaderModule module;
2564 // We may need to link the pipeline just like we'll do with shader module identifiers below.
3252 TCU_FAIL("Not every module has a unique ID");
3346 // Create pipelines using shader module ids. These will actually be run. Note the changing viewports and scissors.
3482 // Test shader module identifier extension properties
3562 // Skip this case for constant module identifiers.
3635 // Tests creating pipelines using the module id extension structures.
3675 // Test creating and using pipelines from shader module identifiers
3768 // Tests checking HLSL tessellation shaders with module identifiers