From owner-freebsd-bugs@freebsd.org Thu Jan 25 01:39:38 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B4E6ED3C78 for ; Thu, 25 Jan 2018 01:39:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB6DA82B72 for ; Thu, 25 Jan 2018 01:39:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1B3D91F9CA for ; Thu, 25 Jan 2018 01:39:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0P1daxG012821 for ; Thu, 25 Jan 2018 01:39:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0P1daoV012820 for freebsd-bugs@FreeBSD.org; Thu, 25 Jan 2018 01:39:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 225182] devel/powerpc64-xtoolchain-gcc: SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc Date: Thu, 25 Jan 2018 01:39:36 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bapt@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 01:39:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225182 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #6 from Mark Millard --- (In reply to Kenneth Salerno from comment #5) Just as a point of reference for a PowerMac G5 context: # uname -apKU FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r327364M powerpc powerp= c64 1200054 1200054 This was built via: A) kernel: devel/powerpc64-xtoolchain-gcc based B) world: system clang 5.0.1 based [I experiment with clang targeting powerpc64 and powerpc.) Both were using devel/powerpc64-binutils . Both were cross builds from an amd64 context. (As seen from the version number, its been a while since I've updated. But it is not far back on the scale you report exploring.) I can list src.conf content used and the like if appropriate. Note: I could also boot and run based on a clang 5.0.1 kernel as long as I made sure no kernel module was dynamically loaded. 5.0.1 is generating a new type of relocation information that the kernel is not handling. With 5.0.0 I used to use a clang-based kernel. It has been a while since I tried it, but I used to be able to also build and install world based on devel/powerpc64-xtoolchain-gcc and it worked. Other notes: If clang builds the system-library support for C++ exception handling, then any thrown exception causes a process crash. clang does not do everything it should for the built-ins involved. --=20 You are receiving this mail because: You are on the CC list for the bug.=