Sparc64 doesn't care about you, and you shouldn't care about Sparc64

[alexmcwhirter at triadic.us]

On 2015-11-06 09:19, Sean Bruno wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> 
> 
> On 11/06/15 01:18, alexmcwhirter at 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-----
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"

As for the first issue, ill take a look a see what im actually dealing 
with. Like i said, i'm working clang/llvm for illumos but that's an 
entirely different beast.

I have access to quite a lot of sparc gear. V215, T1000, T5120, M4000, 
E6K, Netra X1, and a few more. I don't mind hosting a couple of them if 
anyone in interested in doing some work on them.