From owner-freebsd-toolchain@FreeBSD.ORG  Sat Sep 13 08:29:40 2014
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: freebsd-toolchain@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 49F912E5
 for <freebsd-toolchain@freebsd.org>; Sat, 13 Sep 2014 08:29:40 +0000 (UTC)
Received: from vlakno.cz (mail.vlakno.cz [91.217.96.224])
 by mx1.freebsd.org (Postfix) with ESMTP id 08EA1C9B
 for <freebsd-toolchain@freebsd.org>; Sat, 13 Sep 2014 08:29:39 +0000 (UTC)
Received: by vlakno.cz (Postfix, from userid 1002)
 id EA05D1D95D14; Sat, 13 Sep 2014 10:23:22 +0200 (CEST)
Date: Sat, 13 Sep 2014 10:23:22 +0200
From: Roman Divacky <rdivacky@vlakno.cz>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: status of clang on sparc64?
Message-ID: <20140913082322.GA76218@vlakno.cz>
References: <20140912000406.GA83874@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140912000406.GA83874@troutmask.apl.washington.edu>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: freebsd-toolchain@freebsd.org
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 08:29:40 -0000

On Thu, Sep 11, 2014 at 05:04:06PM -0700, Steve Kargl wrote:
> What's the current status for running clang on sparc64?

Last time we played with this (february?) it was able to compile
a seemingly working world. So I guess it's not that terribly broken.

We didnt test that much stuff though.

> In particular, flame.freebsd.org is running 10.1-PRERELEASE
> compiled with gcc 4.2.1.  Any chance that clanf can be
> made available on flame?

I think your best bet is to compile it on flame yourself or crosscompile
world for sparc64 and use it on flame.

Roman