radeonsi: use a threaded context even for debug contexts
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
diff --git a/src/gallium/drivers/radeonsi/si_pipe.c b/src/gallium/drivers/radeonsi/si_pipe.c
index ef5cddd..5fbf1b3 100644
--- a/src/gallium/drivers/radeonsi/si_pipe.c
+++ b/src/gallium/drivers/radeonsi/si_pipe.c
@@ -381,15 +381,8 @@
if (!(flags & PIPE_CONTEXT_PREFER_THREADED))
return ctx;
- /* Clover (compute-only) is unsupported.
- *
- * Since the threaded context creates shader states from the non-driver
- * thread, asynchronous compilation is required for create_{shader}_-
- * state not to use pipe_context. Debug contexts (ddebug) disable
- * asynchronous compilation, so don't use the threaded context with
- * those.
- */
- if (flags & (PIPE_CONTEXT_COMPUTE_ONLY | PIPE_CONTEXT_DEBUG))
+ /* Clover (compute-only) is unsupported. */
+ if (flags & PIPE_CONTEXT_COMPUTE_ONLY)
return ctx;
/* When shaders are logged to stderr, asynchronous compilation is