atomics force the compiler down the complete path.
Originally posted by: MicahVillmow atomics force the compiler down the complete path.
Which leads to the following questions:
1. Can I get a terminating loop with another read construct?
2. Can the compiler be changed in a way, so that it uses "complete path" only for variable affected by atomic operations?
3. Will the OpenCl standard be extented to include global synchronization primitives, so I won't hav to use dirty hacks anymore?