Date: Wed, 04 Dec 2019 23:08:00 +1100 From: Michelle Sullivan <michelle@sorbs.net> To: Chris Ross <cross+freebsd@distal.com>, Mark Linimon <linimon@lonesome.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: Sparc64 and FreeBSD 13.0 Message-ID: <20495159-605f-c0eb-bd26-4daaab2024a2@sorbs.net> In-Reply-To: <D91A6BEA-ED7B-4352-AC68-A0856158BEE3@distal.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>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Ross wrote: > >> On Dec 3, 2019, at 13:11, Mark Linimon <linimon@lonesome.com> wrote: >> >> On Tue, Dec 03, 2019 at 05:53:28AM -0500, Ed Maste wrote: >>> I have received some private mail about addressing the compiler >>> situation on sparc64, but not the other issues tracked as dependencies >>> in PR228919. >> I personally don't intend to spend cycles working on sparc64 in the >> future. >> >> As one of the last people who was supporting it, I think it's fair to >> say that sparc64 has dropped below critical mass. > I was an active user, but lack of support for more modern spare processors and the lack of active use have caused me to step away too. If I had the time to look into porting T1/T2/etc support, and try to get the compiler working, I’d love to have the results. But I do not. > I don't have the skills or I'd do it. -- Michelle Sullivan http://www.mhix.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20495159-605f-c0eb-bd26-4daaab2024a2>