Mesa (master): i965/gen8: add debug code to show FS disasm with jump locations
Jordan Justen
jljusten at kemper.freedesktop.org
Mon Apr 14 17:36:36 UTC 2014
Module: Mesa
Branch: master
Commit: 24c773fb0685e85d9b838e3e956e4b7ad6e71251
URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=24c773fb0685e85d9b838e3e956e4b7ad6e71251
Author: Jordan Justen <jordan.l.justen at intel.com>
Date: Fri Apr 11 17:22:46 2014 -0700
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 <jordan.l.justen at intel.com>
Reviewed-by: Kenneth Graunke <kenneth at whitecape.org>
---
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp b/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
index bb14148..ef95eb0 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 *
More information about the mesa-commit
mailing list