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 testsuite/66005] libgomp make check time is excessive Date: Wed, 28 Jun 2023 11:41:06 +0000 [thread overview] Message-ID: <bug-66005-4-HaVireGmXu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66005-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66005 --- Comment #28 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>: https://gcc.gnu.org/g:b4561b782427cdfe0fac1a869e79a49187817ffe commit r12-9739-gb4561b782427cdfe0fac1a869e79a49187817ffe Author: Thomas Schwinge <thomas@codesourcery.com> Date: Mon May 15 20:00:07 2023 +0200 Support parallel testing in libgomp: fallback Perl 'flock' [PR66005] Follow-up to commit 6c3b30ef9e0578509bdaf59c13da4a212fe6c2ba "Support parallel testing in libgomp, part II [PR66005]" ("..., and enable if 'flock' is available for serializing execution testing"), where we saw: > On my Dell Precision 7530 laptop: > > $ uname -srvi > Linux 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 > $ grep '^model name' < /proc/cpuinfo | uniq -c > 12 model name : Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz > $ nvidia-smi -L > GPU 0: Quadro P1000 (UUID: GPU-e043973b-b52a-d02b-c066-a8fdbf64e8ea) > > ... [...]: case (c) standard configuration, no offloading > configured, [...] > $ \time make check-target-libgomp > > Case (c), baseline; [...]: > > 1180.98user 110.80system 19:36.40elapsed 109%CPU (0avgtext+0avgdata 505148maxresident)k > 1133.22user 111.08system 19:35.75elapsed 105%CPU (0avgtext+0avgdata 505212maxresident)k > > Case (c), parallelized [using 'flock']: > > [...] > -j12 GCC_TEST_PARALLEL_SLOTS=12 > 2591.04user 192.64system 4:44.98elapsed 976%CPU (0avgtext+0avgdata 505216maxresident)k > 2581.23user 195.21system 4:47.51elapsed 965%CPU (0avgtext+0avgdata 505212maxresident)k Quite the same when instead of 'flock' using this fallback Perl 'flock': 2565.23user 194.35system 4:46.77elapsed 962%CPU (0avgtext+0avgdata 505216maxresident)k 2549.38user 200.20system 4:46.08elapsed 961%CPU (0avgtext+0avgdata 505216maxresident)k PR testsuite/66005 gcc/ * doc/install.texi: Document (optional) Perl usage for parallel testing of libgomp. libgomp/ * testsuite/lib/libgomp.exp: 'flock' through stdout. * testsuite/flock: New. * configure.ac (FLOCK): Point to that if no 'flock' available, but 'perl' is. * configure: Regenerate. (cherry picked from commit 04abe1944d30eb18a2060cfcd9695d085f7b4752)
next prev parent reply other threads:[~2023-06-28 11:41 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-04 13:38 [Bug libgomp/66005] New: " ro at gcc dot gnu.org 2022-01-21 20:42 ` [Bug libgomp/66005] " belyshev at depni dot sinp.msu.ru 2022-02-08 14:15 ` tschwinge at gcc dot gnu.org 2022-05-29 5:05 ` egallager at gcc dot gnu.org 2023-05-04 15:29 ` tschwinge at gcc dot gnu.org 2023-05-05 9:05 ` tschwinge at gcc dot gnu.org 2023-05-15 10:11 ` cvs-commit at gcc dot gnu.org 2023-05-15 10:12 ` cvs-commit at gcc dot gnu.org 2023-05-15 10:31 ` [Bug testsuite/66005] " tschwinge at gcc dot gnu.org 2023-05-15 11:15 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-05-15 11:38 ` jakub at gcc dot gnu.org 2023-05-15 14:22 ` tschwinge at gcc dot gnu.org 2023-05-15 18:35 ` tschwinge at gcc dot gnu.org 2023-05-15 20:06 ` egallager at gcc dot gnu.org 2023-05-15 20:22 ` jakub at gcc dot gnu.org 2023-05-15 20:42 ` tschwinge at gcc dot gnu.org 2023-05-16 7:46 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-05-16 7:57 ` jakub at gcc dot gnu.org 2023-06-02 7:51 ` cvs-commit at gcc dot gnu.org 2023-06-02 10:07 ` tschwinge at gcc dot gnu.org 2023-06-02 10:16 ` iains at gcc dot gnu.org 2023-06-05 14:52 ` tschwinge at gcc dot gnu.org 2023-06-23 12:51 ` tschwinge at gcc dot gnu.org 2023-06-23 13:42 ` jakub at gcc dot gnu.org 2023-06-28 11:39 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:39 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:39 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:40 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:41 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:41 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-28 11:42 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:42 ` cvs-commit at gcc dot gnu.org 2023-06-28 11:42 ` cvs-commit 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-66005-4-HaVireGmXu@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: linkBe 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).