From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7485A38708A8; Thu, 14 May 2020 15:16:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7485A38708A8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589469404; bh=73D5yR+1hRflBcGDhdj8GgUr4Wn+Gv/lg/RpC+34wgc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rsI0Mo9mMQpQbFIBIJcuDjCm5Pn2B9tBaDR6xK7cfO2x2motgmtC5Xckr5XqshYsU Y/KxZjLQZH2ab3KtICxj6Y2qiQXY2TmG0kgT5wu7oPl0ALpVAxgwMKfpe/R8RdQQso v5J+PI0nBe1HK3E4u58GXuwzRRyLvzLsvoBBqOf0= From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95119] CLOSE hangs when -fopenmp is specified in compilation Date: Thu, 14 May 2020 15:16:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.3.0 X-Bugzilla-Keywords: openmp, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 15:16:44 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95119 --- Comment #4 from Thomas Koenig --- So, in order for this to hang, two close statements on the same unit are needed, the first one with an error message. Seems like the unit is not unlocked on the error return.=