[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 Dave Evans changed: What|Removed |Added CC||dave.evan...@googlemail.com --- Comme

[Bug 243959] Compilation on powerpc fails with __atomic_compare_exchange_8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243959 Bug ID: 243959 Summary: Compilation on powerpc fails with __atomic_compare_exchange_8 Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any

[Bug 243959] Compilation on powerpc fails with __atomic_compare_exchange_8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243959 Yuri Victorovich changed: What|Removed |Added Blocks||243958 Referenced Bugs: https

[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Commen

[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 --- Comment #3 from Robert Clausecker --- These notes aside: this memory usage is far from the norm for compiling a C++ source file. I believe there must be a bug in clang or llvm or some unfortunate design in the source file itself that c

[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 --- Comment #4 from Mark Millard --- (In reply to Mark Millard from comment #2) I should have noted: if a process stays runnable, FreeBSD does not stop it and swap it out but instead just pages it. (For FreeBSD, swapping basically seems to

[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 --- Comment #5 from Mark Millard --- (In reply to Dave Evans from comment #1) Was this a -j1 build? Something larger? (There could be other things worth reporting about the build context.) It can be interesting to watch the system with to

[Bug 241437] objcopy --add-section doesn't work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241437 --- Comment #2 from Ed Maste --- See https://reviews.freebsd.org/D23571 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https:

[Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 --- Comment #6 from Mark Millard --- (In reply to Mark Millard from comment #5) Looks like vm.pageout_oom_seq goes back to 10.3.0-RELEASE so experiments with it on a 12.0-RELEASE based system should be possible. -- You are receiving this

[Bug 243972] Missing word "be" in rc.conf(5) "hostname" section

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243972 Bug ID: 243972 Summary: Missing word "be" in rc.conf(5) "hostname" section Product: Documentation Version: Latest Hardware: Any OS: Any Status: New

[Bug 243973] [zfs] zfs rollback segmentation fault

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243973 Bug ID: 243973 Summary: [zfs] zfs rollback segmentation fault Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severit

[Bug 243973] [zfs] zfs rollback segmentation fault

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243973 --- Comment #1 from Reshad Patuck --- Created attachment 211467 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211467&action=edit Shell script to reproduce the segfault This shell script reproduces the issue 100% of the time for

[Bug 243973] [zfs] rollback segmentation fault

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243973 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable12?, |