Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Mar 2020 04:45:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 230454] Compiling world fails on /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGCXXABI.cpp
Message-ID:  <bug-230454-29464-SnCOUqNY9F@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-230454-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-230454-29464@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=3D230454

--- Comment #8 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
I'll note that folks have been reporting problems
with 1 GiByte machines for -j1 buildworld's based
on the compilation of gmock-matchers_test.cc .
An example is:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241848

It might be better to make such the base so
the information is not as old as here: declare
older submittals as duplicates of the modern
information example?

(llvm materials have grown as well.)

Head has also added an paging/swapping I/O
related OOM criteria (that was temporarily
broken a littel while back). I've not used
a 1 GiBYTe context but I use two settings,
one of which is for avoiding I/O related
kills happening as easilly:

#
# Delay when persistent low free RAM leads to
# Out Of Memory killing of processes:
vm.pageout_oom_seq=3D120
#
# For plunty of swap/paging space (will not
# run out), avoid pageout delays leading to
# Out Of Memory killing of processes:
vm.pfault_oom_attempts=3D-1

I do this on 2 GiByte+ contexts to better
avoid OOM kills. vm.pfault_oom_attempts is
head-only last I knew but vm.pageout_oom_seq
is much older.

Some folks have used much larger
vm.pageout_oom_seq values.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230454-29464-SnCOUqNY9F>