From owner-freebsd-sparc64@freebsd.org Fri Nov 6 14:19:43 2015 Return-Path: Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83911A2861A; Fri, 6 Nov 2015 14:19:43 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6593517D2; Fri, 6 Nov 2015 14:19:42 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.200.208] (unknown [50.136.155.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 401EE1934F2; Fri, 6 Nov 2015 14:19:41 +0000 (UTC) Subject: Re: Sparc64 doesn't care about you, and you shouldn't care about Sparc64 To: alexmcwhirter@triadic.us References: <563A5893.1030607@freebsd.org> <20151104214451.GF47630@server.rulingia.com> <20151105232431.GE31432@ivaldir.etoilebsd.net> <6189d48d3a178c4ebf501361c75de23f@triadic.us> Cc: freebsd-arch@freebsd.org, freebsd-sparc64 From: Sean Bruno Message-ID: <563CB6FC.209@freebsd.org> Date: Fri, 6 Nov 2015 06:19:40 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <6189d48d3a178c4ebf501361c75de23f@triadic.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2015 14:19:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/06/15 01:18, alexmcwhirter@triadic.us wrote: > So is the problem in question the lack of being able to use > clang/llvm? Or that newer hardware is unsupported? sparc64 supports > sun4u which is most boxes, Fujitsu Sparc64 boxes also work quite > well. The only thing really missing is sun4v and a few drivers here > and there. OpenBSD has support for almost all of the newer > Sun/Oracle boxes, which shouldn't bee too hard to port over. > > http://www.openbsd.org/sparc64.html > > Because of the lack of sun4v support i have moved over to a custom > illumos distro, but one of the things im working on there is to > replace gcc with clang/llvm. If it means saving the sparc64 port i > will gladly move some of my work over to freebsd. problem 1. the base clang/llvm doesn't support the FreeBSD sparc64 target. This needs work, and hey, if someone wants to spend the time to get things working, great. Let's move on it and modernize the target. problem 2. lack of development hardware in the FreeBSD project. I'm not asking for people to buy the FreeBSD project 10-15 year old sparc hardware and send it to us. We don't want it. If there is a push to modernize support for Sparc machines, we can talk about aquiring new machines and racking them up as reference boxes. If there are people interested in modernizing CPU support, by all means, move forward and do it. Don't let me stop you. sean p.s. if someone wants to take a stab at resurrecting qemu-user-static support for sparc64 so portmgr can build tier-2 packages like we do for mips/arm, please take a look at https://github.com/seanbruno/qemu-bsd-user/tree/bsd-user -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJWPLb5XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kaf4H/0C3rHmnFv3dtAyYwEzX4vLy erkQ1MD42czuLuSCcywO/P82u4ytV4Tsc/4A7uJvabQfanZF4s8rBPDdGoodIslO gZhvtMxhojueqtcvZjcLCBX5v3iu0aDL8w6PAafm0QvUUUNft42jbw+nD8l6xF+5 pPpKB0OK6KS3beuSqRGqfLIwAGSSXKjkktm3WaPEHu6N+WNCnA/kPMdLl2VTD7fU SOwkeoE5ItWgeHwQ1V6fr/kbRxJ+QYUxSeN5XeFzkQGM58GlkT2dhjL/y6feU6AO MlvOJhax03+uOGR4sxQOJ+F5ndWPbuZ+Lk64eVQiHoW6nbpKtuAwrAzehD9lg0w= =jW6R -----END PGP SIGNATURE-----