From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 67602385783F; Tue, 16 May 2023 07:58:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 67602385783F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684223880; bh=n1+V+YUTipPnqGQByih/KVZM+6RdLLAMJ3rNg4AAyRo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NMDKCvCQo+YD2Y4IMF92OOPHX3i1kKg9p4c74rJ8H4NDN3jZZckiISNN4vjmnoLGJ fNYhSgPOwlk+yR4h6+U1kcdMIfVnx0zQux/4VxFSbz6h7c9prc1RAhmyucfqg3jglu M10l/fR2SBWwltZcr3UYtDOz04AKwJ6ujS5/MLxU= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/66005] libgomp make check time is excessive Date: Tue, 16 May 2023 07:57:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: openacc, openmp, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: tschwinge 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66005 --- Comment #16 from Jakub Jelinek --- Another possibility would be pick up one runtest (e.g. the first one using O_EXCL which creates some file) and let it perform all executions from that point on instead of doing the compilations, where the other runtest would f= eed what needs to be executed and later deleted say through a pipe. The reading through pipe would ensure that it is able to wait if there is no immediate = work for it. Of course we have dg-set-env-var which complicates things a little bit, probably those would need to be transfered to the execution job togeth= er with what program should run, what options should be passed to it, what LD_LIBRARY_PATH should be used etc. One issue is make sure all the executa= ble names are unique even at all optimization levels, we can't have target1.exe created more than once.=