https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82895
--- Comment #4 from Arjen Markus <arjen.markus at deltares dot nl> --- It was precisely this sort of issues that led me to write this small sample program. And I realised this morning, that indeed the host variables need to be avoided. But does: - loop_body accesses the host-associated, non-threadprivate variables q, x, and id, and you get data races mean that it is utterly unsafe to access even the shared variables (x and id in this case)? That would defy the intentions of using a(n internal) routine altogether. I need to have access to the entire array and the pattern of iterations avoids data collisions. (The I/O was an attempt to understand what was going on, as well as getting slightly more work done per iteration)
