Date: Tue, 17 Dec 2019 14:55:08 -0800 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-sparc64@freebsd.org Subject: Re: Sparc64 and FreeBSD 13.0 Message-ID: <411df638-0f12-81af-eca7-181af93f0230@FreeBSD.org> In-Reply-To: <20191205035843.GA3392@lonesome.com> References: <CAPyFy2CxrOLx9RtA9hA6ou7gb5d-uqvJjCSXVYOoojt37%2Bs%2B9A@mail.gmail.com> <CAPyFy2DJeHB%2BFdnagoVmxMwUGp92YMNSU9Kg7E4n-x55MUvFhA@mail.gmail.com> <20191203181148.GA24129@lonesome.com> <D91A6BEA-ED7B-4352-AC68-A0856158BEE3@distal.com> <20495159-605f-c0eb-bd26-4daaab2024a2@sorbs.net> <CAGuhNT3=fGkgEpHK066g-oQj%2BJUYfWPkYRee3tXG65zAN=bq_Q@mail.gmail.com> <CAK3Ucu6%2BkVpsuR-ZVHSURJe_32Dg6_kwRn69jyD-NxO=UsrL3g@mail.gmail.com> <20191205035843.GA3392@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/4/19 7:58 PM, Mark Linimon wrote: > On Wed, Dec 04, 2019 at 05:34:46PM -0600, Joe Kozak wrote: >> I put my vote of support in for someone doing some updating if >> possible. > > Unfortunately it doesn't work like that in volunteer projects. > > I estimate it would take 1-3 months to fix the toolchain -- which > would only save us the existing systems (manufactured up to 2005). > When I last looked at sun4v (the newer systems) I estimated 3-5 > months. > > That's full-time activity from someone who *used* to do systems > work, but has not for many years, and would have to come up to > speed on 18 zillion things. > > mcl > > (fwiw I am a software engineer, ergo, my estimates suck.) Fixing the toolchain is probably less than 1-3 months. I have a freebsd-gcc9 port that I haven't posted for review yet, but it hits the same snag (assertion failure in ld.bfd) that freebsd-gcc6 hits. I think the assertion failure is wrong and needs to use >= instead of >, but I just haven't sat down and looked at it in a debugger to see the exact values at the time of the assertion failure. However, I think even once you get it building there might be a few more bumps with getting things like PCPU_* working in the kernel correctly. I probably won't get to it anytime soon, and sparc64 really needs multiple active folks to keep it viable. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?411df638-0f12-81af-eca7-181af93f0230>