From 7f71efcf7a8eace124e71ca72c86d4c2bdc8042d Mon Sep 17 00:00:00 2001 From: Tom Stellard Date: Mon, 10 Dec 2012 16:04:04 +0000 Subject: clover: Don't erase build info of devices not being built Every call to _cl_program::build() was erasing the binaries and logs for every device associated with the program. This is incorrect because it is possible to build a program for only a subset of devices and so any device not being build should not have this information erased. Reviewed-by: Francisco Jerez --- src/gallium/state_trackers/clover/core/program.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/gallium/state_trackers') diff --git a/src/gallium/state_trackers/clover/core/program.cpp b/src/gallium/state_trackers/clover/core/program.cpp index 6ca8080c925..5fcda23fc65 100644 --- a/src/gallium/state_trackers/clover/core/program.cpp +++ b/src/gallium/state_trackers/clover/core/program.cpp @@ -42,10 +42,10 @@ _cl_program::_cl_program(clover::context &ctx, void _cl_program::build(const std::vector &devs) { - __binaries.clear(); - __logs.clear(); for (auto dev : devs) { + __binaries.erase(dev); + __logs.erase(dev); try { auto module = (dev->ir_format() == PIPE_SHADER_IR_TGSI ? compile_program_tgsi(__source) : -- cgit v1.2.3