Displaying 3 results from an estimated 3 matches for "bar_0".
Did you mean:
bar0
2012 Dec 01
0
[LLVMdev] [RFC] "noclone" function attribute
...onInto) will still work [...].
Unfortunately, it won't work.
Assume all threads call foo:
foo() {
...
bar(i)
...
}
bar(int i) {
...
barrier();
...
}
Now, suppose that we have discovered that bar(0) can be greatly
optimized and generate a call to the specialized version, bar_0:
foo() {
...
if (i == 0) bar_0();
else bar(i);
...
}
And now we have multiple threads that no longer have a common barrier.
-Krzysztof
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
2012 Dec 01
6
[LLVMdev] [RFC] "noclone" function attribute
Hi,
OpenCL has a "barrier" function with very specific semantics, and there is currently no analogue to model this in LLVM.
This has been touched on by the SPIR folks but I don't believe they put forward a proposal.
The barrier function is a special function that ensures that all workitems executing a kernel have executed up to that point before execution on any workitem can
2012 Dec 01
3
[LLVMdev] [RFC] "noclone" function attribute
...ionInto) will still work [...].
Unfortunately, it won't work.
Assume all threads call foo:
foo() {
...
bar(i)
...
}
bar(int i) {
...
barrier();
...
}
Now, suppose that we have discovered that bar(0) can be greatly
optimized and generate a call to the specialized version, bar_0:
foo() {
...
if (i == 0) bar_0();
else bar(i);
...
}
And now we have multiple threads that no longer have a common barrier.
-Krzysztof
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
_____________________________________...