public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95119] [9/10 Regression] CLOSE hangs when -fopenmp is specified in compilation
Date: Fri, 22 May 2020 14:08:51 +0000	[thread overview]
Message-ID: <bug-95119-4-dxXjSnrqjk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95119-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95119

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Thomas Kथà¤nig
<tkoenig@gcc.gnu.org>:

https://gcc.gnu.org/g:f1d34396c264ae15ba7492bd2b800c5764d92134

commit r9-8615-gf1d34396c264ae15ba7492bd2b800c5764d92134
Author: Thomas Koenig <tkoenig@gcc.gnu.org>
Date:   Thu May 14 18:30:27 2020 +0200

    Add early return for invalid STATUS for close.

    2020-05-14  Thomas Koenig  <tkoenig@gcc.gnu.org>

            PR libfortran/95119
            * io/close.c (close_status): Add CLOSE_INVALID.
            (st_close): Return early on invalid STATUS parameter.

    2020-05-14  Thomas Koenig  <tkoenig@gcc.gnu.org>

            PR libfortran/95119
            * testsuite/libgomp.fortran/close_errors_1.f90: New test.

    (cherry picked from commit cdc34b505796327b3eee9e97bc5f27ba71fd9e7a)
    (cherry picked from commit d975519ad1066ed0397714c91aafadadb52a63dd)
    (cherry picked from commit 8275e0a6686b465d4d1717784e3e864305d37d02)

  parent reply	other threads:[~2020-05-22 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 22:28 [Bug fortran/95119] New: " longb at cray dot com
2020-05-13 22:35 ` [Bug fortran/95119] " longb at cray dot com
2020-05-14  5:45 ` tkoenig at gcc dot gnu.org
2020-05-14  6:46 ` tkoenig at gcc dot gnu.org
2020-05-14 15:16 ` tkoenig at gcc dot gnu.org
2020-05-14 16:12 ` tkoenig at gcc dot gnu.org
2020-05-14 16:34 ` cvs-commit at gcc dot gnu.org
2020-05-14 16:50 ` [Bug fortran/95119] [9/10 Regression] " tkoenig at gcc dot gnu.org
2020-05-22 14:02 ` cvs-commit at gcc dot gnu.org
2020-05-22 14:08 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-22 14:09 ` tkoenig at gcc dot gnu.org
2020-05-22 16:10 ` tkoenig at gcc dot gnu.org
2020-10-18 20:50 ` longb at cray dot com
2020-10-19  5:31 ` tkoenig 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-95119-4-dxXjSnrqjk@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).