nir: Lock around validation fail shader dumping
authorJason Ekstrand <jason@jlekstrand.net>
Wed, 27 Mar 2019 15:13:28 +0000 (10:13 -0500)
committerJason Ekstrand <jason@jlekstrand.net>
Sat, 30 Mar 2019 02:57:51 +0000 (21:57 -0500)
This prevents getting mixed-up results if a multi-threaded app has two
validation errors in different threads.

Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
src/compiler/nir/nir_validate.c

index 80f397098a2955fd895525274619c7d8242f6547..5f812974720b9d1f91936fdafce83367b4440437 100644 (file)
@@ -26,6 +26,7 @@
  */
 
 #include "nir.h"
+#include "c11/threads.h"
 #include <assert.h>
 
 /*
@@ -1180,11 +1181,18 @@ destroy_validate_state(validate_state *state)
    _mesa_hash_table_destroy(state->errors, NULL);
 }
 
+mtx_t fail_dump_mutex = _MTX_INITIALIZER_NP;
+
 static void
 dump_errors(validate_state *state, const char *when)
 {
    struct hash_table *errors = state->errors;
 
+   /* Lock around dumping so that we get clean dumps in a multi-threaded
+    * scenario
+    */
+   mtx_lock(&fail_dump_mutex);
+
    if (when) {
       fprintf(stderr, "NIR validation failed %s\n", when);
       fprintf(stderr, "%d errors:\n", _mesa_hash_table_num_entries(errors));
@@ -1203,6 +1211,8 @@ dump_errors(validate_state *state, const char *when)
       }
    }
 
+   mtx_unlock(&fail_dump_mutex);
+
    abort();
 }