summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJordan Justen <[email protected]>2014-04-11 17:22:46 -0700
committerJordan Justen <[email protected]>2014-04-14 10:32:42 -0700
commit24c773fb0685e85d9b838e3e956e4b7ad6e71251 (patch)
treea2298b3992ec6b80b1f656fc5b6e14b97e3b1c15
parent73a47610587d55c06e2d7af13192baada163b114 (diff)
i965/gen8: add debug code to show FS disasm with jump locations
Copied from similar code in gen8_vec4_generator.cpp. Signed-off-by: Jordan Justen <[email protected]> Reviewed-by: Kenneth Graunke <[email protected]>
-rw-r--r--src/mesa/drivers/dri/i965/gen8_fs_generator.cpp9
1 files changed, 9 insertions, 0 deletions
diff --git a/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp b/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
index bb141485d6e..ef95eb0275e 100644
--- a/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
+++ b/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
@@ -1268,6 +1268,15 @@ gen8_fs_generator::generate_code(exec_list *instructions)
}
patch_jump_targets();
+
+ /* OK, while the INTEL_DEBUG=fs above is very nice for debugging FS
+ * emit issues, it doesn't get the jump distances into the output,
+ * which is often something we want to debug. So this is here in
+ * case you're doing that.
+ */
+ if (0 && unlikely(INTEL_DEBUG & DEBUG_WM)) {
+ disassemble(stderr, 0, next_inst_offset);
+ }
}
const unsigned *