diff options
| author | Alejandro Piñeiro <apinheiro@igalia.com> | 2015-10-01 16:41:30 +0200 |
|---|---|---|
| committer | Alejandro Piñeiro <apinheiro@igalia.com> | 2015-10-22 21:58:03 +0200 |
| commit | 92ae101ed0dff689f207abf61f68167009de4e29 (patch) | |
| tree | d0d23265eaba1a3be00e617bd55f684a22d51c1b /src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp | |
| parent | 8fc8fcc04f584b32cd5bf633da8e3508249e339d (diff) | |
| download | external_mesa3d-92ae101ed0dff689f207abf61f68167009de4e29.zip external_mesa3d-92ae101ed0dff689f207abf61f68167009de4e29.tar.gz external_mesa3d-92ae101ed0dff689f207abf61f68167009de4e29.tar.bz2 | |
i965/vec4: use an envvar to decide to print the assembly on cmod_propagation tests
The complete way to do this would be parse INTEL_DEBUG and
print the output if DEBUG_VS (or a new one) is present
(see intel_debug.c).
But that seems like an overkill for the unit tests, that
after all, the most common use case is being run when
calling make check.
v2: use the same idea for the fs counterpart too, as suggested by
Matt Turner
Reviewed-by: Matt Turner <mattst88@gmail.com>
Diffstat (limited to 'src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp')
| -rw-r--r-- | src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp b/src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp index 5f80f90..62d39f7 100644 --- a/src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp +++ b/src/mesa/drivers/dri/i965/test_fs_cmod_propagation.cpp @@ -84,7 +84,7 @@ instruction(bblock_t *block, int num) static bool cmod_propagation(fs_visitor *v) { - const bool print = false; + const bool print = getenv("TEST_DEBUG"); if (print) { fprintf(stderr, "= Before =\n"); |