Closed adrieng closed 5 years ago
Thanks for the question. Exiting a cilk_for
via control flow, such as break
or return
, is not supported. There are newer versions of Tapir that will catch and report these cases as errors, but we haven't backported those changes to master
. (And, unfortunately, we've been remiss in keeping Tapir-Meta up to date.)
That makes sense. Thanks @neboat!
Hi! Is exiting a cilk_for via control-flow (break/return) supported? I've run into various issues trying to compile the following function.
Trying to compile without optimizations, I get the following error:
The error gets uglier after enabling optimizations:
I've attached the files mentioned above in test-940b5d.zip.
As far as I see, the above crash is deterministic. Replacing
return
withbreak
leads to non-deterministic, infrequent crashes.The crash I sometimes get is:
Here are the log files for this second crash.