https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
--- Comment #9 from Jakub Jelinek ---
OpenMP just says that a structured block
"may contain STOP or ERROR STOP statements."
and nothing else, what the particular behavior for STOP is is covered in the
base language or is up to the implementation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
Thomas Koenig changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
--- Comment #6 from Dominique d'Humieres ---
> Nay progress after more than two years?
No progress after more than three more years?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
--- Comment #4 from Bud Davis ---
Upon closer reflection, the underlying problems is the OpenMP threads doing I/O
while the units are being closed.
So, stop shows in the output, followed by output from threads whose units have
been destroyed, but
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
Bud Davis changed:
What|Removed |Added
CC||bdavis at gcc dot gnu.org
--- Comment #3 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
--- Comment #2 from Janne Blomqvist 2011-12-17 11:27:40
UTC ---
Looks like some kind of race condition..
E.g. what about: STOP calls exit(), which leads to the library destructor being
called, which calls close_units(), which closes each open u
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
Tobias Burnus changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #1 from
