Date: Wed, 11 Mar 2020 07:06:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile Message-ID: <bug-241848-227-XLthrgClV6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241848-227@https.bugs.freebsd.org/bugzilla/> References: <bug-241848-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241848 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dim@FreeBSD.org --- Comment #15 from Dimitry Andric <dim@FreeBSD.org> --- This particular source file is indeed a rather pathological case. On my 13.0-CURRENT test system, using clang 10.0.0-rc3 (with assertions enabled), it takes a maxrss of 1982620, so ~1936 MiB to compile with -O2. Gcc 9.2.0 from ports fares even worse, it takes about 20% more time to comp= ile, and a maxrss of 2684812, so ~2622 MiB. I also tried the clang90 port, but this assertions disabled, and this takes= a maxrss of 1755320, so ~1714 MiB. For now, my advice would be to compile this file with -O1, or even -O0, as = it seems to be an internal test for googletest itself, and not something that = we actively need to have heavily optimized. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241848-227-XLthrgClV6>