diff options
| author | Erico Nunes <[email protected]> | 2019-08-03 10:56:12 +0200 |
|---|---|---|
| committer | Erico Nunes <[email protected]> | 2019-08-06 15:43:31 +0200 |
| commit | e0aeee946004685527dfa0a4f5f141b85ae076dd (patch) | |
| tree | 84377b66fb5c5f8b9e237b6aae65ae7038c886c4 /src/gallium/drivers/lima/lima_screen.h | |
| parent | 9e41a514a8aabe209e7cc999a609c9a0a252b3d7 (diff) | |
lima: add summary report for shader-db
Very basic summary, loops and gpir spills:fills are not updated yet and
are only there to comply with the strings to shader-db report.py regex.
For now it can be used to analyze the impact of changes in instruction
count in both gpir and ppir.
The LIMA_DEBUG=shaderdb setting can be useful to output stats on
applications other than shader-db.
Signed-off-by: Erico Nunes <[email protected]>
Reviewed-by: Qiang Yu <[email protected]>
Diffstat (limited to 'src/gallium/drivers/lima/lima_screen.h')
| -rw-r--r-- | src/gallium/drivers/lima/lima_screen.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gallium/drivers/lima/lima_screen.h b/src/gallium/drivers/lima/lima_screen.h index 7d1f6f82924..29693168828 100644 --- a/src/gallium/drivers/lima/lima_screen.h +++ b/src/gallium/drivers/lima/lima_screen.h @@ -36,6 +36,7 @@ #define LIMA_DEBUG_GP (1 << 0) #define LIMA_DEBUG_PP (1 << 1) #define LIMA_DEBUG_DUMP (1 << 2) +#define LIMA_DEBUG_SHADERDB (1 << 3) extern uint32_t lima_debug; extern FILE *lima_dump_command_stream; |