i965: Move program key debugging to the compiler.
The i965 driver has a bunch of code to compare two sets of program keys and print out the differences. This can be useful for debugging why a shader needed to be recompiled on the fly due to non-orthogonal state dependencies. anv doesn't do recompiles, so we didn't need to share this in the past - but I'd like to use it in iris. This moves the bulk of the code to the compiler where it can be reused. To make that possible, we need to decouple it from i965 - we can't get at the brw program cache directly, nor use brw_context to print things. Instead, we use compiler->shader_perf_log(), and simply pass in keys. We put all of this debugging code in brw_debug_recompile.c, and only export a single function, for simplicity. I also tidied the code a bit while moving it, now that it all lives in one file. Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
This commit is contained in:
@@ -1348,6 +1348,10 @@ brw_compile_cs(const struct brw_compiler *compiler, void *log_data,
|
||||
int shader_time_index,
|
||||
char **error_str);
|
||||
|
||||
void brw_debug_key_recompile(const struct brw_compiler *c, void *log,
|
||||
gl_shader_stage stage,
|
||||
const void *old_key, const void *key);
|
||||
|
||||
static inline uint32_t
|
||||
encode_slm_size(unsigned gen, uint32_t bytes)
|
||||
{
|
||||
|
Reference in New Issue
Block a user