public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51591] Strange output from STOP statement in OpenMP region
Date: Sat, 11 May 2013 17:09:00 -0000	[thread overview]
Message-ID: <bug-51591-4-ATYLIumNAy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51591-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591

--- Comment #4 from Bud Davis <bdavis at gcc dot gnu.org> ---
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 the call to exit() handler has not yet terminated.


  parent reply	other threads:[~2013-05-11 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 22:31 [Bug fortran/51591] New: " longb at cray dot com
2011-12-17 10:21 ` [Bug fortran/51591] " burnus at gcc dot gnu.org
2011-12-17 11:32 ` jb at gcc dot gnu.org
2012-02-03 22:09 ` bdavis at gcc dot gnu.org
2013-05-11 17:09 ` bdavis at gcc dot gnu.org [this message]
2015-10-20 14:54 ` dominiq at lps dot ens.fr
2020-07-30 15:17 ` dominiq at lps dot ens.fr
2020-07-30 15:23 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-51591-4-ATYLIumNAy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).