Drop ir3_compiler_destroy(), since it is only ralloc_free() and we
shouldn't really have an ir3 dependency in core. If some future hw
has a new compiler, as long as all it's resources are ralloc()d then
things will all just work.
(In practice, I suppose you never really see this leak, but removing
it at least cleans up some noise in valgrind.)
Signed-off-by: Rob Clark <robdclark@gmail.com>
mtx_destroy(&screen->lock);
+ ralloc_free(screen->compiler);
+
free(screen);
}
compiler->set = ir3_ra_alloc_reg_set(compiler);
return compiler;
}
-
-void ir3_compiler_destroy(struct ir3_compiler *compiler)
-{
- ralloc_free(compiler);
-}
};
struct ir3_compiler * ir3_compiler_create(struct fd_device *dev, uint32_t gpu_id);
-void ir3_compiler_destroy(struct ir3_compiler *compiler);
int ir3_compile_shader_nir(struct ir3_compiler *compiler,
struct ir3_shader_variant *so);