Date: Wed, 15 Jan 2020 09:53:28 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 243182] java/openjdk11: add bootstrap and fix compilation for powerpc64 elfv2 Message-ID: <bug-243182-25139-4VCmqXhMvW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243182-25139@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243182 --- Comment #13 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Piotr Kubaj from comment #12) The case for system-clang's use for powerpc64 is currently even stronger: > . . . > You definitely could build FreeBSD without Clang and use external GCC on ELFv2 > . . . devel/freebsd-gcc9@powerpc64 (set up to use ELFv2) and devel/binutils@powerpc64 are, together, not yet sufficient to buildworld buildkernel . The GNU ld.bfd goes into a unbounded loop during buildworld; for example, while trying to link lld together. (I've reported that loop code and its behavior upstream.) I've not tried devel/freebsd-gcc6@powerpc64 for ELFv2. But gcc6 is beyond the gcc folks supporting it at this point. I hope that at some point at least 2 modern toolchains support buildworld buildkernel producing working code, including booting. (I also hope for effective ABI compatibility.) system-clang + devel/binutils@powerpc64 produces a kernel that crashes. (For all I know, both the binutils and the kernel contribute to the mismatches are at runtime that lead to the kernel crashing.) -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243182-25139-4VCmqXhMvW>