From owner-freebsd-arch@FreeBSD.ORG Sun Apr 6 21:56:35 2014 Return-Path: <owner-freebsd-arch@FreeBSD.ORG> Delivered-To: freebsd-arch@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 3D2D95EF for <freebsd-arch@freebsd.org>; Sun, 6 Apr 2014 21:56:35 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2F44E0 for <freebsd-arch@freebsd.org>; Sun, 6 Apr 2014 21:56:34 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id lx4so5443760iec.38 for <freebsd-arch@freebsd.org>; Sun, 06 Apr 2014 14:56:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=FAV8J86MypwqsrPpxkALYu1tr/Sszj/0Vd2/luHOkpY=; b=k7VnbAVflbpNL/KzT2pzRP4oyMhomPm+c4UyiYWSQtfXjBpyDvSgCFn5KVXZa7ywMs IsVyp7u/CjNAVZpIJjRnlrKynuk1Zb3k/t0z27CSeilzPBi30o3cdmoRenIATQjYaYHh pja6P42z67bc6rvRJQA/bar2Dp2aiouAGHLfAgSDG7HpJC1qHg/pDGf/3Dyz/m+XRb1v 7X2PwScm+GKAYpU6oNz2IyJyhEhcO3EQ1oNdj4U9b/7lTzIy56V3uirxQCw2f+tEJKkh dNspRPFyHwZd6UAA7e9pDG75swXOAhEoxtZqwMk+bOhLt2Iqxins0AgRCsI4hkDcwu9f XAIA== X-Gm-Message-State: ALoCoQnwshfNftXi+BUyzl1HvMnqXjoXtY17V6u0aoEHzy4TE8qs95IbhRc00SEk2/ofNwe2sa9M X-Received: by 10.50.143.34 with SMTP id sb2mr16550262igb.11.1396821387760; Sun, 06 Apr 2014 14:56:27 -0700 (PDT) Received: from [10.0.0.119] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id u1sm24684443igm.8.2014.04.06.14.56.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 06 Apr 2014 14:56:27 -0700 (PDT) Sender: Warner Losh <wlosh@bsdimp.com> Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Compiler toolchain roadmap From: Warner Losh <imp@bsdimp.com> In-Reply-To: <EB9CE8A8-E897-4DE1-A8BC-80C6CC23E612@ixsystems.com> Date: Sun, 6 Apr 2014 15:56:26 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9E11A6D4-9D18-422D-9514-4714AADDAEF4@gmail.com> References: <201404021607.s32G7mhw051355@svn.freebsd.org> <20140404115256.GA85137@ivaldir.etoilebsd.net> <F2A33EA8-14F2-4D62-9021-9023A1751E48@FreeBSD.org> <8D6AF193-A5A3-4A28-A230-97A543395ACA@ixsystems.com> <2E0EC8CB-B3EE-4DB8-A33D-58FD2107F14D@FreeBSD.org> <6A02504F-5543-4F91-92F6-7B4FB9A34DC4@ixsystems.com> <152D73EE-DF9E-4757-B547-F1F22B12C824@FreeBSD.org> <B06E1588-8828-485F-A407-3F19231F8EA5@ixsystems.com> <8E3BD3C1-A441-48C5-97BC-45EF67513096@FreeBSD.org> <6418BE83-BE78-473B-9311-C849507FA885@ixsystems.com> <CAJ-Vmom-19LujsTQ+v4XozE+iEH18LMEQitBLC-At=DmsgkB+Q@mail.gmail.com> <EB9CE8A8-E897-4DE1-A8BC-80C6CC23E612@ixsystems.com> To: Jordan Hubbard <jkh@ixsystems.com> X-Mailer: Apple Mail (2.1874) Cc: freebsd-arch <freebsd-arch@freebsd.org> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org> List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>, <mailto:freebsd-arch-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 06 Apr 2014 21:56:35 -0000 On Apr 6, 2014, at 4:16 AM, Jordan Hubbard <jkh@ixsystems.com> wrote: > Now it=92s 2014 and apparently we can=92t have nice things in the tree = because of MIPS? Maybe I=92m over-simplifying the argument, but even = simplistically I would easily understand First off, nobody every said we can=92t have nice things in the tree = because of MIPS. Where was that said? It can=92t possibly be true = because gcc supports blocks in the tree, so there=92s no impediment. = LLVM-based things? Show me the money and bring one to the table and we = can talk, but even then there=92s clang support for mips, so again = that=92s not a big deal. As for numbers, perhaps you are right about mips, perhaps not. There=92s = a thriving community, the code isn=92t holding the tree back, and things = do get fixed there. Maybe not as well as our ARM community, but it still = us. I hear a lot of FUD and chest pounding about how it is holding us = back, but I=92ve yet to see any real evidence of that proffered. Mips = and powerpc are in the tree because Juniper needs/wants them, and has = been contributing fixes to the tree over the years. External toolchain is coming along nicely given the timelines for 11, = which is where we committed to having it done and removing gcc/binutils = from the tree. clang is good, but it isn=92t quite ready for the = binutils removal yet. If the time comes and it isn=92t done, then we can = talk about how mips is holding things up (assuming the clang mips stuff = doesn=92t go in). But until then, show me the concrete examples where = there=92s an actual problem. Warner