Re: devel/llvm13 failed to reclaim memory on 8 GB Pi4 running -current

On Fri, 28 Jan 2022, Mark Millard wrote:

[ Reviving old thread ]

> After that I intend runs with 30 GiBytes of swap (so RAM+SWAP 38 GiBytes).
> Hopefully that will complete and I'll be able to report how much swap was
> observed to have been used.

I thought I will get LLVM14 + OpenJDK built quickly so I fired up
a c6g.4xlarge AWS instance (16 vCPUs, 32 GB RAM),
or even c6g.8xlarge (32 vCPUs, 64 GB RAM) and even these
are unable to build llvm14 under FreeBSD 13.1-RELEASE
with poudriÚre enabling MAKE_JOBS for llvm build.

The build proceeds on 1 CPU only now - and casual observation
with top confirms that compilation of certain C++ files
requires 7..8 GB of RAM. If 16 of them are built concurrently,
no wonder that there is not enough memory.

Files tha crashed my compiliation:

/wrkdirs/usr/ports/devel/llvm14/work/llvm-project-14.0.4.src/flang/lib/Evaluate/tools.cpp
/wrkdirs/usr/ports/devel/llvm14/work/llvm-project-14.0.4.src/clang/lib/Sema/SemaOpenMP.cpp
/wrkdirs/usr/ports/devel/llvm14/work/llvm-project-14.0.4.src/flang/lib/Semantics/check-omp-structure.cpp
/wrkdirs/usr/ports/devel/llvm14/work/llvm-project-14.0.4.src/flang/lib/Evaluate/fold-integer.cpp

Sure, poudriÚre could get Kubernetes-like capabilities to control
resources during the build one day, but aren't amounts of memory
needed to build the compiler excessive a bit?

saper