From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5F00A3858D28; Mon, 7 Feb 2022 15:43:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5F00A3858D28 From: "vries at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/104423] New: [libgomp, testsuite] Add means to do accelerator-only testing in libgomp Date: Mon, 07 Feb 2022 15:43:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: Mon, 07 Feb 2022 15:43:04 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104423 Bug ID: 104423 Summary: [libgomp, testsuite] Add means to do accelerator-only testing in libgomp Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- For nvptx offload testing, I switched to an eGPU setup, and cycle through 4 boards (kepler, maxwell, pascal, turing) to do pre-commit testing. Sometim= e in the future that'll be 5, once I get an ampere board as well. I run a script test-board.sh that iterates over various dimensions, which t= akes about 5 hours per board. In practice, this means testing a patch get spread over 2 days. Furthermore, I'm looking to extend the dimensions on which I test, possibly doubling the test-board time. I noticed that a lot of time is spent running libgomp tests that do not use= the accelerator, and which are not needed for my purposes. It would be nice if libgomp provided a mode to run only tests that use the accelerator, to drive down the test-board.sh execution time.=