May 2019 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Wed May 1 00:08:47 UTC 2019
Ending: Wed May 29 18:28:26 UTC 2019
Messages: 197

• 2-socket/2-cores-each G5 PowerMac11, 2: I show the initial slb content *before* the FreeBSD kernel makes changes   Mark Millard
• 32-bit powerpc: bjam stuck compute-bound during poudriere bulk build of devel/boost-libs (during staging)   Mark Millard
• 32-bit powerpc: bjam stuck compute-bound during poudriere bulk build of devel/boost-libs (during staging)   Mark Millard
• 32-bit powerpc: bjam stuck compute-bound during poudriere bulk build of devel/boost-libs (during staging)   Mark Millard
• 32-bit powerpc FreeBSD head -r347549 ports -r501994: lang/ruby25 build via poudriere failed via SIGSEGV in lib/csu/powerpc/crtsavres.S   Mark Millard
• 970/G5 powerpc64: why are HIOR (311), HID0, HID1 set in cpudep_ap_setup *AFTER* cpudep_ap_bootstrap tries general PSL_IR|PSL_DR activity for pcpup->pc_curthread->td_pcb->   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Justin Hibbits
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Andreas Tobler
• 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .   Mark Millard
• 970MP PowerMac G5s: What printf's show about cpu_mp_unleash hangups on the test variant of head -r347003 (found cpu_mp_unleash counterexample)   Mark Millard
• 970MP PowerMac G5s: What printf's show about cpu_mp_unleash hangups on the test variant of head -r347003 (found cpu_mp_unleash counterexample)   Mark Millard
• 970MP PowerMac G5s: What printf's show about cpu_mp_unleash hangups on the test variant of head -r347003 (surprising, important)   Mark Millard
• 970MP PowerMac G5s: What some basic printf's show about vt_upgrade and fhanew_init hang-ups   Mark Millard
• [Bug 232060] lang/mono: Fix for Mono build on FreeBSD PowerPC   bugzilla-noreply at freebsd.org
• [Bug 232387] head -r345558 (updated): system crash during kldload if_epair on powerpc64 (for more modern buildworld buildkernel toolchain experiments), Probably also: ipfw.ko linuxkpi.ko siftr.ko   bugzilla-noreply at freebsd.org
• [Bug 232387] head -r345558 (updated): system crash during kldload if_epair on powerpc64 (for more modern buildworld buildkernel toolchain experiments), Probably also: ipfw.ko linuxkpi.ko siftr.ko   bugzilla-noreply at freebsd.org
• [Bug 232387] head -r345558 (updated): system crash during kldload if_epair on powerpc64 (for more modern buildworld buildkernel toolchain experiments), Probably also: ipfw.ko linuxkpi.ko siftr.ko   bugzilla-noreply at freebsd.org
• [Bug 233807] devel/msbuild Fails on PowerPC64   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 235060] [boot] FreeBSD 12.0 Release DVD and CD will not boot on PowerMac G5 Quad   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237208] java/openjdk11: port to powerpc64   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237370] java/openjdk12: Add powerpc64 support   bugzilla-noreply at freebsd.org
• [Bug 237471] [PowerPC64] pseries llan driver wrong MAC address   bugzilla-noreply at freebsd.org
• An experiment in PowerMac G5 multi-socket/multi-core having better matching mftb() values   Mark Millard
• An experiment in PowerMac G5 multi-socket/multi-core having better matching mftb() values   Mark Millard
• An experiment in PowerMac G5 multi-socket/multi-core having better matching mftb() values   Mark Millard
• Building Firefox on powerpc64   Francis Little
• Building Firefox on powerpc64   Jan Beich
• cpudep_ap_early_bootstrap: IBM970 SPR_HID4 and SPR_HID5 updates are not following documented, 970-family-specific rules   Mark Millard
• cpudep_ap_early_bootstrap: IBM970 SPR_HID4 and SPR_HID5 updates are not following documented, 970-family-specific rules   Mark Millard
• cpudep_ap_early_bootstrap: IBM970 SPR_HID4 and SPR_HID5 updates are not following documented, 970-family-specific rules   Mark Millard
• CTR2(KTR_PMAP, "moea64_bootstrap: kstack0 at %#x (%#x)", pa, va); truncates va values for powerpc64   Mark Millard
• Examples of early boot variability in handle_kernel_slb_spill happening on 2-socket/2-core-each G5 PowerMac11,2   Mark Millard
• Fwd: svn commit: r347492 - head/lib/libc/powerpc64/string   Justin Hibbits
• Fwd: svn commit: r347492 - head/lib/libc/powerpc64/string   Dennis Clarke
• FYI: Unable to build -r501994 ports' devel/llvm60 on clang 8 based powerpc64 system: "BFD (GNU Binutils) 2.32 assertion fail elflink.c:2935"   Mark Millard
• FYI: Unable to build -r501994 ports' devel/llvm60 on clang 8 based powerpc64 system: "BFD (GNU Binutils) 2.32 assertion fail elflink.c:2935"   Dimitry Andric
• FYI: Unable to build -r501994 ports' devel/llvm60 on clang 8 based powerpc64 system: "BFD (GNU Binutils) 2.32 assertion fail elflink.c:2935"   Mark Millard
• FYI: Unable to build -r501994 ports' devel/llvm60 on clang 8 based powerpc64 system: "BFD (GNU Binutils) 2.32 assertion fail elflink.c:2935"   Mark Millard
• FYI: Unable to build -r501994 ports' devel/llvm60 on clang 8 based powerpc64 system: "BFD (GNU Binutils) 2.32 assertion fail elflink.c:2935"   Mark Millard
• FYI: Unable to build -r501994 ports' devel/qt5-core on clang 8 based powerpc64 system: "Q_ATOMIC_INT64_IS_SUPPORTED must be defined on a 64-bit platform"   Mark Millard
• FYI: Unable to build -r501994 ports' devel/qt5-core on clang 8 based powerpc64 system: "Q_ATOMIC_INT64_IS_SUPPORTED must be defined on a 64-bit platform"   Mark Millard
• FYI: Unable to build -r501994 ports' lang/gcc8 on clang 8 based powerpc64 system (no -O1 use): "does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or ..."   Mark Millard
• FYI: Unable to build -r501994 ports' lang/gcc8 on clang 8 based powerpc64 system (no -O1 use): "does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or ..."   Mark Millard
• FYI: Unable to build -r501994 ports' lang/gcc8 on clang 8 based powerpc64 system (no -O1 use): "does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or ..."   Mark Millard
• gem0 instability   Jason Bacon
• gem0 instability   Michael Tuexen
• gem0 instability   Jason Bacon
• Global Blockchain IoT Market 2019-2026   David Smith
• head -r347003 on 2-socket/2-cores-each G5 PowerMac11, 2's: one type of boot-blocking context found   Mark Millard
• head -r347003 on 2-socket/2-cores-each G5 PowerMac11,2's: one type of boot-blocking context found   Justin Hibbits
• head -r347003 on 2-socket/2-cores-each G5 PowerMac11,2's: one type of boot-blocking context found   Mark Millard
• head -r347003 on 2-socket/2-cores-each G5 PowerMac11,2's: one type of boot-blocking context found   Mark Millard
• head -r347003 on 2-socket/2-cores-each G5 PowerMac11,2's: one type of boot-blocking context found (CPU 1 evidence)   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Justin Hibbits
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Justin Hibbits
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Justin Hibbits
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• How many segments does it take to span from VM_MIN_KERNEL_ADDRESS through VM_MAX_SAFE_KERNEL_ADDRESS? 128 in moea64_late_bootstrap   Mark Millard
• Installing FreeBSD 12 on a POWER7   Georg Bege
• kernel mode EXC_DSE handling depends on td->td_pcb-> not slb faulting in setting up its slbmte use?   Mark Millard
• kernel mode EXC_DSE handling depends on td->td_pcb-> not slb faulting in setting up its slbmte use?   Mark Millard
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Francis Little
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Mark Millard
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Justin Hibbits
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Justin Hibbits
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Alan Braslau
• Mac G5 X11 performance   Jason Bacon
• Mac G5 X11 performance   Alan Braslau
• moea64_cpu_bootstrap_native slbmte (and such) use: missing context synchronizations (isync's)?   Mark Millard
• moea64_cpu_bootstrap_native slbmte (and such) use: missing context synchronizations (isync's)?   Mark Millard
• n_slbs==32 vs. restore_kernsrs use of slbmte in its loop   Mark Millard
• PowerMac G5's and such: Should HIOR save/restore be involved in ofw_save_trap_vec and ofw_restore_trap_vec?   Mark Millard
• PowerMac G5's vs. PSL_ME manipulation in the msr: mtmsr ignores it, only rfid can set it? (How to avoid checkstop on the ap's?)   Mark Millard
• PowerMac G5 context: kernel_va_to_slbv(...) and SLBV_L use vs. addresses < DMAP_BASE_ADDRESS   Mark Millard
• PowerMac G5 live slb entries before moea64_mid_bootstrap for bsp vs. later: are duplications of ESID's avoided?   Mark Millard
• powerpc64: kern_slbtrap double mtlr, one from (PC_SLBSAVE+120)(%r1) and one from (PC_SLBSAVE+136)(%r1)?   Mark Millard
• powerpc64 and 32-bit powerpc: get_cyclecount is messed up for both (presuming reliability is required)   Mark Millard
• powerpc64 context: aim/locore64.S __start TMPSTKSZ-48 vs. TMPSTKSZ-96 (-r277392 and later) vs. modern aim/trap_subr64.S cpu_reset_handler: (TMPSTKSZ-48)?   Mark Millard
• powerpc64 context: aim/locore64.S __start TMPSTKSZ-48 vs. TMPSTKSZ-96 (-r277392 and later) vs. modern aim/trap_subr64.S cpu_reset_handler: (TMPSTKSZ-48)?   Mark Millard
• powerpc64 context: aim/locore64.S __start TMPSTKSZ-48 vs. TMPSTKSZ-96 (-r277392 and later) vs. modern aim/trap_subr64.S cpu_reset_handler: (TMPSTKSZ-48)?   Mark Millard
• powerpc64 context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"   Mark Millard
• powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"   Mark Millard
• powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"   Ralf Wenk
• powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"   Mark Millard
• powerpc64 graphics/mesa-dri build failure in poudriere, system clang's /usr/bin/cc got assert failure: "Target supports vector op, but scalar requires expansion?"   Jan Beich
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Linimon
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Jason Bacon
• powerpc64 system-clang-8 based context: x11-toolkits/qt5-declarative fails to build in poudriere: /usr/local/lib/qt5/bin/qlalr segmentation faults in std::type_info::~type_info() () from /usr/local/lib/gcc8/libstdc++.so.6   Mark Millard
• Remote Firewire dcons use shows my G5 "hang-up point" reports have been wrong: shows lines not shown on the problem context's display   Mark Millard
• Remote Firewire dcons use shows my G5 "hang-up point" reports have been wrong: shows lines not shown on the problem context's display   Mark Millard
• slbmte, slbie, slbia isync paranoyia for -r347003 investigation: does it change any behavior as stands? (yes)   Mark Millard
• The first 2 handle_kernel_slb_spill calls on the 2-socket/2-cores-each G5 example context: as expected? (short)   Mark Millard
• The first 2 handle_kernel_slb_spill calls on the 2-socket/2-cores-each G5 example context: as expected? (short)   Mark Millard
• The first 2 handle_kernel_slb_spill calls on the 2-socket/2-cores-each G5 example context: as expected? (short)   Mark Millard
• The first 2 handle_kernel_slb_spill calls on the 2-socket/2-cores-each G5 example context: as expected? (short)   Mark Millard
• Tiny summary of todays explorations: __pcpu[] has no reserved kernel slb entry(s) to cover it; slbmte and the like missing some isync use   Mark Millard
• X.org colour issues on PowerMac G5 with GeForce 6600   Francis Little
• X.org colour issues on PowerMac G5 with GeForce 6600   Francis Little

Last message date: Wed May 29 18:28:26 UTC 2019
Archived on: Wed May 29 18:28:29 UTC 2019

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...