panfrost: Don't leak NIR blend shaders
Right now we create shaders that are not attached to any memory context, leading to memory leaks. Ideally, we should free the NIR shader as soon as we've turned it into a binary, but there's no function explicitly destroy a shader. Let's attach those to the blend state so they get destroyed when this state is freed. Signed-off-by:Boris Brezillon <boris.brezillon@collabora.com> Reviewed-by:
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <mesa/mesa!7066>
Showing
- src/gallium/drivers/panfrost/pan_blend_cso.c 1 addition, 1 deletionsrc/gallium/drivers/panfrost/pan_blend_cso.c
- src/gallium/drivers/panfrost/pan_blend_shaders.c 3 additions, 4 deletionssrc/gallium/drivers/panfrost/pan_blend_shaders.c
- src/gallium/drivers/panfrost/pan_blend_shaders.h 1 addition, 1 deletionsrc/gallium/drivers/panfrost/pan_blend_shaders.h
Loading
Please register or sign in to comment