| /freebsd/lib/googletest/tests/ |
| H A D | Makefile.inc | 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| H A D | Makefile | diff 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/tests/gmock/ |
| H A D | Makefile | 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/tests/gtest_main/ |
| H A D | Makefile | 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/tests/gtest/ |
| H A D | Makefile | 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/tests/gmock_main/ |
| H A D | Makefile | 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/gmock_main/ |
| H A D | Makefile | diff 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/gtest_main/ |
| H A D | Makefile | diff 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/gmock/ |
| H A D | Makefile | diff 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|
| /freebsd/lib/googletest/gtest/ |
| H A D | Makefile | diff 2ed3236082a4473c1da8f72c1ebc071a7b54321f Mon Oct 19 21:50:57 CEST 2020 Alex Richardson <arichardson@FreeBSD.org> Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library.
However, each of these is serialized at the top level makefile.
Additionally some of the tests (e.g. the gmock-matches-test) take up to
90 seconds to build with clang -O2. Having to wait for this test to
complete before continuing to the next directory seriously slows down the
parllelism of a -j32 build.
Before this change running `make -C lib/googletest -j32 -s` in buildenv
took 202 seconds, now it's 153 due to improved parallelism.
Reviewed By: emaste (no objection)
Differential Revision: https://reviews.freebsd.org/D26748
|