After SPIRV->NIR, the driver shouldn't rely on the module. This will
still report messages via VK_EXT_debug_report but the object will be
NULL.
Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15766>
* from the implementation and layers.
*/
vk_debug_report(&instance->vk, vk_flags[level] | VK_DEBUG_REPORT_DEBUG_BIT_EXT,
- &debug_data->module->base, 0, 0, "radv", message);
+ NULL, 0, 0, "radv", message);
}
static bool
struct radv_shader_debug_data debug_data = {
.device = device,
- .module = module,
+ .module = NULL,
};
options->family = chip_family;