Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-30, at 7:51 PM, Mark Millard <markmi_at_dsl-only.net> wrote:

> On 2017-Mar-30, at 1:22 PM, Mark Millard <markmi_at_dsl-only.net> wrote:
> 
>> Sounds like the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG technique
>> would not change the "WITNESS and INVARIANTS"-like part of the
>> issue. In fact if WITH_DEBUG= causes the cmake debug-style
>> llvm40 build ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG might not
>> make any difference: separate enforcing of lack of optimization.
>> 
>> But just to see what results I've done "pkg delete llvm40"
>> and am doing another build with ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG=
>> and its supporting code in place in addition to using WITH_DEBUG=
>> as the type of build fro FreeBSD's viewpoint.
>> 
>> If you know that the test is a waste of machine cycles, you can
>> let me know if you want.
> 
> The experiment showed that ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG
> use made no difference for devel/llvm40 so devel/llvm40 itself
> has to change such as what Dimitry Andric reported separately
> as a working change to the Makefile .
> 
> (ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG would still have its uses
> for various other ports.)

I've now tried with both ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG and:

# svnlite diff /usr/ports/devel/llvm40/
Index: /usr/ports/devel/llvm40/Makefile
===================================================================
--- /usr/ports/devel/llvm40/Makefile	(revision 436747)
+++ /usr/ports/devel/llvm40/Makefile	(working copy)
_at__at_ -236,6 +236,11 _at__at_
 
 .include <bsd.port.pre.mk>
 
+.if defined(WITH_DEBUG)
+CMAKE_BUILD_TYPE=	RelWithDebInfo
+STRIP=
+.endif
+
 _CRTLIBDIR=	${LLVM_PREFIX:S|${PREFIX}/||}/lib/clang/${LLVM_RELEASE}/lib/freebsd
 .if ${ARCH} == "amd64"
 _COMPILER_RT_LIBS= \



pkg delete after the build reports:

Installed packages to be REMOVED:
	llvm40-4.0.0

Number of packages to be removed: 1

The operation will free 42 GiB.

So down by 7 GiBytes from 49 GiBytes.

(I did not actually delete it.)

Also:

# du -sg /usr/obj/portswork/usr/ports/devel/llvm40
102	/usr/obj/portswork/usr/ports/devel/llvm40

which is down by 16 GiBytes from 118 GiBytes.

Reminder: These are from portmaster -DK so no
cleanup after the build, which is what leaves
the source code and such around in case of
needing to look at a problem.

(102+42) GiBytes == 146 GiBytes.
vs.
(118+49) GiBytes == 167 GiBytes.

So a difference of 21 GiBytes (or so).

But that is for everything in each case (and
WITH_DEBUG= in use):

# more /var/db/ports/devel_llvm40/options
# This file is auto-generated by 'make config'.
# Options for llvm40-4.0.0.r4
_OPTIONS_READ=llvm40-4.0.0.r4
_FILE_COMPLETE_OPTIONS_LIST=CLANG DOCS EXTRAS LIT LLD LLDB
OPTIONS_FILE_SET+=CLANG
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_SET+=EXTRAS
OPTIONS_FILE_SET+=LIT
OPTIONS_FILE_SET+=LLD
OPTIONS_FILE_SET+=LLDB

So avoiding WITH_DEBUG= and/or various build options
is still the major way of avoiding use of lots of space
if it is an issue.



Why no RAM+SWAP total report this time:

As far as I know FreeBSD does not track or report peak
swap-space usage since the last boot. And, unfortunately
I was not around to just sit and watch a top display this
time and I did not set up any periodic recording into a
file.

That is why I've not reported on the RAM+SWAP total
this time. It will have to be another experiment
some other time.

[I do wish FreeBSD had a way of reporting peak swap-space
usage.]

===
Mark Millard
markmi at dsl-only.net