From owner-freebsd-sparc64@FreeBSD.ORG  Thu Jan 16 21:31:09 2014
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 310F3AB2
 for <sparc64@freebsd.org>; Thu, 16 Jan 2014 21:31:09 +0000 (UTC)
Received: from vlakno.cz (mail.vlakno.cz [95.129.96.251])
 by mx1.freebsd.org (Postfix) with ESMTP id E81621B2F
 for <sparc64@freebsd.org>; Thu, 16 Jan 2014 21:31:08 +0000 (UTC)
Received: by vlakno.cz (Postfix, from userid 1002)
 id 9FB481CC55CC; Thu, 16 Jan 2014 22:31:01 +0100 (CET)
Date: Thu, 16 Jan 2014 22:31:01 +0100
From: Roman Divacky <rdivacky@freebsd.org>
To: sparc64@freebsd.org
Subject: Call for help: clang/llvm for sparc64
Message-ID: <20140116213101.GA33444@freebsd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8"
Content-Disposition: inline
User-Agent: Mutt/1.5.22 (2013-10-16)
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64/>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
 <mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 21:31:09 -0000


--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi!

LLVM is getting a sparc64 backend. It can even selfhost on linux. But it cant
on FreeBSD. I am wondering what causes that difference.

A small test case where the difference can be seen is compiling tcsh from
base. The gethost utility used during the build just coredumps. I suspect
fixing that might get us on par with linux.

So I am looking for someone who is willing to compile llvm/clang and
analyze whats wrong with gethost in tcsh compilation.

This is how to do it (you need trunk llvm/clang):

svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
cd llvm/
svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
cd ../
CFLAGS=-fno-strict-aliasing CXXFLAGS=-fno-strict-aliasing ./configure --enable-optimized --enable-targets=sparc64
make
make install

will give you a clang binary that you can use for tcsh compilation:

cd /usr/src/bin/csh
CC=clang make

I am more than willing to help with llvm/clang side of this but I dont know
anything about sparc64 so I need help. But please contact me if you want to
help!

Thanks, Roman

--MGYHOYXEY6WxJCY8
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iEYEARECAAYFAlLYT5UACgkQLVEj6D3CBExz8ACeJJPnJ7OCBXOgO9asM3kiAqiJ
P5QAnjVehUozz6/kHzo1OQWBGB8R+vOs
=ZXrr
-----END PGP SIGNATURE-----

--MGYHOYXEY6WxJCY8--