[Bug 230454] Compiling world fails on /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGCXXABI.cpp

2020-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230454

--- Comment #8 from Mark Millard  ---
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=241848

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=120
#
# 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=-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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"


[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

2020-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153

--- Comment #16 from Mark Millard  ---
Head -352175 added ET_DYN to _kvm_probe_elf_kernel
and ET_DYN is what started this.

As stands dump hangs on the old PowerMac G5s.
So I'm unable to produce such powerpc64 dumps
to see what the libkvm handling it like.

I gather that the main line of development is
on more modern hardware and is not seeing such
problems --so dumps are being used via libkvm
from what I can tell.

It appears that someone with a powerpc64
environment that can dump would have to check
on the status of this. I'm blocked at an
earlier stage.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"


[Bug 215039] head -r339076 TARGET_ARCH=powerpc64 clang 6.0.1 based buildworld on powerpc64 using WITH_LLVM_LIBUNWIND= fails to build: asserts and rejects .S file contents

2020-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215039

Mark Millard  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #5 from Mark Millard  ---
Things have progressed to powerpc64 and 32-bit powerpc
being built by llvm (more recent versions), including
use of its libunwind. The reported problem is gone.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"