From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EC2493986008; Thu, 7 May 2020 21:05:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC2493986008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588885515; bh=oeC3s6OAKkFVsw/+rGIKycxR1mmI/u1k5vpUVyw090s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TTDD1bKAAVzbPyGQPjAj0Ubq8v3eoCHwruhM0Lghta+gyEg8vGOc8ubehu7vuHgnK hkXgNGoCBqDXi8W08ZiT/K72D5rm4+1ZQBnVNI6a02CEvUh3aRvynV20lLKoTHd82r YJW+eqprl6g0wfArp+2IS/H+NM6MTdzKUgTEied0= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/94143] [9/10/11 Regression] Asynchronous execute_command_line() breaks following synchronous calls Date: Thu, 07 May 2020 21:05:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 9.2.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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, 07 May 2020 21:05:16 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94143 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #3 from anlauf at gcc dot gnu.org --- Funny. I do not get failures when compiling with -fsanitize=3Dthread. With valgrind --tool=3Dhelgrind I get lots of "Possible data race" hints that I'm not sure how to interpret.=