From 803337f3f64fed240e9adc6f286d5f9d13a5026a Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Fri, 19 May 2017 12:33:28 +0200 Subject: \0;115;0cCycles: Cleanup, use ccl_restrict instead of ccl_restrict_ptr There were following issues with ccl_restrict_ptr: - We already had ccl_restrict for all platforms. - It was secretly adding `const` qualifier to the declaration, which is quite weird since non-const pointer can also be declared as restricted. - We never in Blender are using foo_ptr or FooPtr type definitions, so not sure why we should introduce such a thing here. - It is absolutely wrong from semantic point of view to put pointer into the restrict macro -- const is a part of type, not part of hint for compiler that some pointer is never aliased. --- intern/cycles/kernel/kernel_compat_cpu.h | 2 -- 1 file changed, 2 deletions(-) (limited to 'intern/cycles/kernel/kernel_compat_cpu.h') diff --git a/intern/cycles/kernel/kernel_compat_cpu.h b/intern/cycles/kernel/kernel_compat_cpu.h index 7595e74e2d5..21da180bb8e 100644 --- a/intern/cycles/kernel/kernel_compat_cpu.h +++ b/intern/cycles/kernel/kernel_compat_cpu.h @@ -42,8 +42,6 @@ #include "util/util_types.h" #include "util/util_texture.h" -#define ccl_restrict_ptr const * __restrict - #define ccl_addr_space #define ccl_local_id(d) 0 -- cgit v1.2.3