public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/66005] New: libgomp make check time is excessive Date: Mon, 04 May 2015 13:38:00 -0000 [thread overview] Message-ID: <bug-66005-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66005 Bug ID: 66005 Summary: libgomp make check time is excessive Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: jakub at gcc dot gnu.org, tschwinge at gcc dot gnu.org Target Milestone: --- With all those OpenACC tests having been added to the libgomp testsuite, make check times have skyrocketed on the gcc 5 branch and mainline: On a reasonably fast x86 machine, it takes 4286 seconds: Test Run By ro on Sat May 2 00:56:49 2015 runtest completed at Sat May 2 02:08:15 2015 while e.g. on slower sparc boxes we're at 29406 seconds: Test Run By ro on Fri May 1 18:38:07 2015 runtest completed at Sat May 2 02:48:13 2015 while for 4.9 we had only 7825 seconds: Test Run By ro on Sat May 2 17:20:23 2015 runtest completed at Sat May 2 19:30:48 2015 Being sequential, the libgomp testsuite is the last to finish, slowing down the whole test. Rainer
next reply other threads:[~2015-05-04 13:38 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-04 13:38 ro at gcc dot gnu.org [this message] 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 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@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).