From owner-freebsd-hackers@freebsd.org Wed Aug 12 23:46:02 2015 Return-Path: Delivered-To: freebsd-hackers@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 5C6139A0D11 for ; Wed, 12 Aug 2015 23:46:02 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 243408; Wed, 12 Aug 2015 23:46:02 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: by oip136 with SMTP id 136so18039740oip.1; Wed, 12 Aug 2015 16:46:01 -0700 (PDT) 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=AAQBKPN6RIdmAW2kAvqziRFfDOBDwVZRitpu3yQBJQM=; b=D4KgCwSGneE2t+StG5OHMiFJTVXqoIsNN54bf6Y5s8+w3AO0vSYY5F2sVWjyeEfJfE oH8bTC2sPtT+GKAfbXvl/p1oCA4JjbFy9gD/Ba4Lj597ehTNs9TJBZfC+Dh2atNHwpa7 l24UwVKOcCTnQsgcs+j9Y5pakOYmB/023fRUNbwEQRqWTm+BG3hZr950X7BnkGczfr8E gQtl1gMtDR2PtV/t44QEGSwGJ/O4JucnZOHMUZ+XUATg89fNEtxv38XBnW9h1TjX6SGV YvK7ySy8x2L+1NIrlkzcZ4QrcJYviwncJw4t7w6es0khEgoozGkmzLGV7g6ADjA2oJwG H4HQ== MIME-Version: 1.0 X-Received: by 10.202.0.206 with SMTP id 197mr26115454oia.15.1439423161241; Wed, 12 Aug 2015 16:46:01 -0700 (PDT) Received: by 10.202.129.139 with HTTP; Wed, 12 Aug 2015 16:46:01 -0700 (PDT) In-Reply-To: <7311511.ISQt3RZVgq@ralph.baldwin.cx> References: <7311511.ISQt3RZVgq@ralph.baldwin.cx> Date: Wed, 12 Aug 2015 18:46:01 -0500 Message-ID: Subject: Re: Sparc64 support From: Bill Sorenson To: John Baldwin Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2015 23:46:02 -0000 I just spent a day building clang36 from ports on one of my idle sparc machines, and it builds a working ubench binary. I'm going to see if I can build some ports with it but thus far the latest clang seems at least superficially functional on sparc. I know when I tired many moons ago, clang built binaries would instantly dump. -Bill Sorenson On Fri, Aug 7, 2015 at 2:53 PM, John Baldwin wrote: > On Wednesday, August 05, 2015 02:10:34 PM Bill Sorenson wrote: > > I'm one of probably a few users of FreeBSD and OpenBSD on multiple > > platforms left and I thought I'd share some of my experience with BSD on > > some of the lesser used platforms. > > Realistically, the major potential bump in the road for sparc64 is the > toolchain. GCC 4.2.1 is getting really long in the tooth and as a > Project we want to drop it as our system compiler. I can't tell you > when that will happen, but it will eventually. That means that all of > our supported platforms will either have to work with clang, or they will > need to use an external GCC toolchain (of more recent vintage). Ensuring > that one of these routes work for sparc64 will make it much easier for > sparc64 to stay in the tree without inhibiting other work. > > My understanding is that the most recent clang in HEAD can at least build > and install on sparc64, but that programs built with it might segfault, > etc. If you are up for debugging those issues then that is one approach. > I do think that clang works on Linux/sparc64, so that these should be > FreeBSD bugs moreso than clang/llvm bugs (but I can't promise that). > > In theory we have bits in our build system to use an external toolchain > for building a system. I haven't worked with them but I have seen others > talk about them (e.g. imp@ and bapt@). Getting the recipe down for how > to do it and testing that the system works with recent versions of > GCC is what is missing there I think (so that there are instructions of > 'install port foo', 'stick this in /etc/make.conf', or 'put this on the > command line to buildworld', etc.). Of course, testing that the resulting > binaries also work correctly would also be good. :) > > -- > John Baldwin >