I think I've encountered a compiler bug that causes the index variable in cilk_for loops to be declared in their parent's scope. I've observed it for gcc 4.8 and 4.9. I've only been able to reproduce the bug when the cilk_for loops appear in templatized code. I've attached a minimal working example which you can compile to reproduce the bug. The relevant portion of code demonstrating the bug is also at the end of this post.
Cheers,
Tim
template<typename T>
void foo() {
cilk_for(int i = 0; i < 5; i++) {
printf("Loop iter: %d",i);
}
// Will get redeclaration error for 'int i'.
cilk_for(int i = 0; i < 5; i++) {
printf("Loop iter: %d",i);
}
}
void bar() {
cilk_for(int i = 0; i < 5; i++) {
printf("Loop iter: %d",i);
}
cilk_for(int i = 0; i < 5; i++) {
printf("Loop iter: %d",i);
}
}
int main(int argc, char **argv)
{
bar(); // compiles.
foo<int>(); // doesn't compile.
return 0;
}
