diff options
| author | Nicolai Hähnle <[email protected]> | 2015-12-08 17:56:23 -0500 |
|---|---|---|
| committer | Nicolai Hähnle <[email protected]> | 2015-12-12 15:23:50 -0500 |
| commit | d640f179d314abef4d82bf3237197f1278415d36 (patch) | |
| tree | 7c57fbf8ff591edca5a76a10c73e762ec3f23105 /src | |
| parent | b86d5ccae2b6280ad26d1060295fcc4963e90011 (diff) | |
gallium/ddebug: regularly log the total number of draw calls
This helps in the use of GALLIUM_DDEBUG_SKIP: first run a target application
with skip set to a very large number and note how many draw calls happen
before the bug. Then re-run, skipping the corresponding number of calls.
Despite the additional run, this can still be much faster than not skipping
anything.
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src')
| -rw-r--r-- | src/gallium/drivers/ddebug/dd_draw.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/gallium/drivers/ddebug/dd_draw.c b/src/gallium/drivers/ddebug/dd_draw.c index 0778099d4fd..0d7ee9a1686 100644 --- a/src/gallium/drivers/ddebug/dd_draw.c +++ b/src/gallium/drivers/ddebug/dd_draw.c @@ -623,6 +623,9 @@ dd_after_draw(struct dd_context *dctx, struct dd_call *call) } ++dctx->num_draw_calls; + if (dscreen->skip_count && dctx->num_draw_calls % 10000 == 0) + fprintf(stderr, "Gallium debugger reached %u draw calls.\n", + dctx->num_draw_calls); } static void |