Date: Thu, 25 May 2017 17:29:10 -0700 From: Mark Millard <markmi@dsl-only.net> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Message-ID: <E425E6E4-3609-4CA0-A9E2-B40AE3CA4758@dsl-only.net> In-Reply-To: <45696549-B3B7-4080-AB2B-7A1DC0966C81@FreeBSD.org> References: <bug-26519-7604@http.bugs.llvm.org/> <bug-26519-7604-UhFFHDCAay@http.bugs.llvm.org/> <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <408D3509-3D62-4413-986B-6C1171FB6138@dsl-only.net> <AA9DF5DF-37D6-4E41-A5EF-D93B9F17D0F9@dsl-only.net> <45696549-B3B7-4080-AB2B-7A1DC0966C81@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-May-25, at 4:31 PM, Dimitry Andric <dim at FreeBSD.org> wrote: > On 25 May 2017, at 23:59, Mark Millard <markmi at dsl-only.net> wrote: >> >> Is llvm bugzilla's latest 26519 fix going to make it >> into release/11.1.0 ? This fixes the last known stack >> handling ABI violation for targeting powerpc FreeBSD >> (32-bit). > > I just committed it in r318906. It should make 11.1-RELEASE. Would be > nice if we can finally close PR 206990. :) To my knowledge there are no more stack handling problems and use of the update should provide evidence that 206990 can be closed. But it may be a while before I update to direct use of something after head -r317820. . . I've frozen at head -317820 while trying to get evidence for a periodic powerpc kernel panic in that version (kernel built with gcc 4.2.1, worlds via both compilers). Small adjustments that change the kernel memory layout a little tend to change the behavior, usually meaning no obvious symptoms. So updating to some other version likely just hides the problem. Unfortunately it frequently takes hours for the panic to occur and so a long time to conclude the panic is not likely to happen in any test that I have running. It may be that I just will not identify anything that points at anything fairly specific to fix but I've not given up yet. What I know of for powerpc's clang status with the stack handling fixes in place is: A) Handling thrown C++ exceptions crashes for code generated by clang. (powerpc64 also has this property.) B) A clang-based kernel fails to start /sbin/init and then gets a data alignment panic. Past investigations relative to (A) suggest multiple problems are around that contribute, it is not just one simple problem. I've not looked at (B) yet. === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E425E6E4-3609-4CA0-A9E2-B40AE3CA4758>