From owner-freebsd-arch@freebsd.org  Sat Oct  7 19:20:27 2017
Return-Path: <owner-freebsd-arch@freebsd.org>
Delivered-To: freebsd-arch@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 E52D3E3FF20;
 Sat,  7 Oct 2017 19:20:27 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.soaustin.net",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 580F7183A;
 Sat,  7 Oct 2017 19:20:26 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from lonesome.com (bones.soaustin.net [192.108.105.22])
 by mail.soaustin.net (Postfix) with ESMTPSA id 9F053738;
 Sat,  7 Oct 2017 14:20:25 -0500 (CDT)
Date: Sat, 7 Oct 2017 14:20:24 -0500
From: Mark Linimon <linimon@lonesome.com>
To: "K. Macy" <kmacy@freebsd.org>
Cc: "A. Wilcox" <AWilcox@wilcox-tech.com>, freebsd-arch@freebsd.org,
 freebsd-sparc64@freebsd.org
Subject: Re: future of sparc64 (was: Making C++11 a hard requirement for
 FreeBSD)
Message-ID: <20171007192024.GA21581@lonesome.com>
References: <CANCZdfq5=KRp4NYKsc15gyS9C7CxrBFxcKQLPwnb_0oPb15vJw@mail.gmail.com>
 <20171005234149.GE8557@spindle.one-eyed-alien.net>
 <59D6CA6C.1040502@Wilcox-Tech.com>
 <20171007174124.GA20810@lonesome.com>
 <CAHM0Q_PuYhnaiQif0w_0gf_ip6QG0sCmMSFj=2xxq4RT42+Emg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHM0Q_PuYhnaiQif0w_0gf_ip6QG0sCmMSFj=2xxq4RT42+Emg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Oct 2017 19:20:28 -0000

On Sat, Oct 07, 2017 at 07:06:29PM +0000, K. Macy wrote:
> I think that FreeBSD needs to always have one big-endian arch

IMHO it keeps things honest.  fwiw, if you fix a port on sparc64 it
will usually fix it on powerpc64 and vice versa (~80% correlation).

But powerpc64 has a (hardware) future and sparc64 doesn't.  I run both
at home, but not the powerpc64 continuously.  (Actually first typed
"4U" it as "$U".  Same idea.)

So, I'm willing to help keep it going (and even loan a machine to the
effort), but I am overcommitted in other areas already.

mcl