[Bug 220184] clang 4.0.0 segfaults on buildworld

[bugzilla-noreply at freebsd.org]

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

--- Comment #5 from Mark Millard <markmi at dsl-only.net> ---
(In reply to Chris Collins from comment #4)

Chris wrote:

I did read elsewhere tho that clang 4.0 has a bug which when it uses too much
memory it will segfault.


"too much memory": probably meaning more than
RAM+swap for the overall system activity, possibly
not having limited to -j1 . -j1 avoid RAM for
parallel processes, trading off time.



In some cases the OS might kill processes
instead of just having memory allocation calls
return failure.

I have used clang 4 for something that on a
machine with 16 GiBytes of RAM required
something like 10 GiBytes of swap as well
before the compiles and links were able to
finish. (This was actually an attempt to
build what turned out to be a debug version
of clang 4, where debug means far more than
just -g use.)

Once sufficient swap was present it completed:
it needed more than 24 GiBytes of "memory
space" overall --more than the machine had
for RAM. (Note: lld and the system linker do
not work well/fully for powerpc64 or powerpc
so this was using devel/powerpc64-binutils .)

(I do not remember if this was for -j4 or -j1
on that old PowerMac G5 so-called "Quad Core".)

I have never involved ccache.



Overall: the variability suggests either
hardware unreliability and/or RAM+swap
limitations for what you are attempting
(given clang 4's and other tool's memory
usage for the -j<?> in use or analogous
for ports).

-- 
You are receiving this mail because:
You are the assignee for the bug.