This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Tweak libgomp env vars in parallel make check
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Martin Liška <mliska at suse dot cz>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 23 Nov 2018 15:09:49 +0100
- Subject: Re: [RFC] Tweak libgomp env vars in parallel make check
- References: <20181123134901.GA12380@tucnak> <bf8037b5-9ad9-9639-d916-65cefbc2809a@suse.cz>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Nov 23, 2018 at 02:57:44PM +0100, Martin Liška wrote:
> > Unfortunately, haven't figured out how to convince automake that I want to
> > write my own check-am goal, so had to drop dejagnu automake option and
> > add all the dejagnu stuff manually.
>
> Do it (at least partially) address https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66005 ?
That PR doesn't contain details (how many CPUs did the machines have, was it
parallel make check and with what -jN), so hard to guess.
The patch certainly doesn't try to parallelize libgomp testsuite (i.e. run
more than one libgomp test at the same time).
I'll see how much does it help in real-world testing later tonight.
All I can say from my logs is that on a quiet machine the patched libgomp
make check-target-libgomp -j2 took 648s,
make check-target-libgomp took 618s.
Last night (nonpatched libgomp) and make -j32 -k check of everything
libgomp took 1912s. And two days ago, concurrent x86_64-linux and i686-linux
make -j32 -k check of everything libgomp took 2626s (x86_64) and 3300s (i686).
All times are wall clock in between the timestamps at the beginning and end
of testsuite/libgomp.log.
Jakub