From owner-freebsd-arch@freebsd.org  Wed Nov  4 22:13:30 2015
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 F2C29A264BF;
 Wed,  4 Nov 2015 22:13:29 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com
 [IPv6:2607:f8b0:4001:c05::22c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id BCE18198E;
 Wed,  4 Nov 2015 22:13:29 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: by igdg1 with SMTP id g1so116583657igd.1;
 Wed, 04 Nov 2015 14:13:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=S3lOD38R2JQcJpR7AxQU3DR8u7eEu9c8G6hIBB4s1lw=;
 b=CNqMHK7HV3JDAB+uWhuS/GaB4x3mPFNkzVouE6p1y/WpwAJvKDgxO4mt4dM77+97Ug
 /TEYgA5o3yuV0gDgSzdYkSZENmfYf186kp95p/uh7wn13ZCohQHU2ELWdmDydybGiJ5V
 mpB3zPrzgDueDpQzRfuxDLE1xJJlUxbV+4Ks1u1nE7HEIhPEQ8KwmY1udyFUdfS9KBa/
 brFr/p2Zp0nmrDUvsmL2qBxIhSQ5J4ZQDlk9YQk2K0yn9/Mce+HByjvuFMoCRki8oFTH
 FsnQ8/XA0kIJjkrHS210ydbj+Wa3M2lu6eWr7PCuhV0tC70AN5XRlrGtrvTZyOdXspKj
 gokA==
MIME-Version: 1.0
X-Received: by 10.50.164.196 with SMTP id ys4mr6285616igb.37.1446675209260;
 Wed, 04 Nov 2015 14:13:29 -0800 (PST)
Received: by 10.36.46.66 with HTTP; Wed, 4 Nov 2015 14:13:29 -0800 (PST)
In-Reply-To: <20151104214451.GF47630@server.rulingia.com>
References: <563A5893.1030607@freebsd.org>
 <20151104214451.GF47630@server.rulingia.com>
Date: Wed, 4 Nov 2015 14:13:29 -0800
Message-ID: <CAJ-VmokSfg_iuNP-MBT9VxHoxVbhGEkWtN6Oiy_ezbmhVMeteg@mail.gmail.com>
Subject: Re: Sparc64 doesn't care about you,
 and you shouldn't care about Sparc64
From: Adrian Chadd <adrian.chadd@gmail.com>
To: Peter Jeremy <peter@rulingia.com>
Cc: Sean Bruno <sbruno@freebsd.org>,
 freebsd-sparc64 <freebsd-sparc64@freebsd.org>, 
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.20
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: Wed, 04 Nov 2015 22:13:30 -0000

We don't have to expect clang support to work. Just having someone
champion the external toolchain stuff and getting sparc64
world/kernel/release building from say, sparc64-gcc 5.x would be
enough.

The hardware support and such is a separate problem. I'd just like
someone there to bite the bullet and push through external toolchain
support for sparc64 and removing the use of gcc-4.2 there.


-a