summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorErik Faye-Lund <[email protected]>2019-11-27 16:30:29 +0100
committerErik Faye-Lund <[email protected]>2019-11-29 09:54:25 +0100
commit49f53ee336e0cc0ad89ab1a8178c4d751dd09de8 (patch)
treef89d78fa5d3462ebf704ecea096cbc9219deb4d2
parentf2188e58cea14c4b4e05634b7b82c4743d1c5c1d (diff)
zink: delete query rather than allocating a new one
It seems I had some fat fingers when writing this function, and I accidentally ended up allocating a new query and immediately trying to delete an uninitialized pool instead of just deleting the pool of the query that was passed. CoverityID: 1455196 Reviewed-by: Dave Airlie <[email protected]>
-rw-r--r--src/gallium/drivers/zink/zink_query.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/drivers/zink/zink_query.c b/src/gallium/drivers/zink/zink_query.c
index 615bd2b9368..e8ed72a1da5 100644
--- a/src/gallium/drivers/zink/zink_query.c
+++ b/src/gallium/drivers/zink/zink_query.c
@@ -80,7 +80,7 @@ zink_destroy_query(struct pipe_context *pctx,
struct pipe_query *q)
{
struct zink_screen *screen = zink_screen(pctx->screen);
- struct zink_query *query = CALLOC_STRUCT(zink_query);
+ struct zink_query *query = (struct zink_query *)q;
vkDestroyQueryPool(screen->dev, query->query_pool, NULL);
}