From owner-freebsd-arch@FreeBSD.ORG Mon Jan 14 03:56:49 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 81A7975A for ; Mon, 14 Jan 2013 03:56:49 +0000 (UTC) (envelope-from peter@wemm.org) Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3E336FFC for ; Mon, 14 Jan 2013 03:56:49 +0000 (UTC) Received: by mail-vb0-f50.google.com with SMTP id ft2so3112201vbb.23 for ; Sun, 13 Jan 2013 19:56:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=G2RBvgyFUhHQTAraTfXe/+n239lPjGgcvIlCpLJfgaE=; b=1OUVKCQtwBmWPWuDM7EAnqlEQFVN+CbPF5J5cjF/E7I8n5kRPTbEspFt4piGwb4t2B URTOl01lAIJcMDdm7/52PHiTlOJa4HrvG9J+SyBx2GVcohiZh7K1FgxLuyW1fut7FtIl 7E5LKfUMe5RTeVsH01/RRwsjepkolSPuUjnsM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=G2RBvgyFUhHQTAraTfXe/+n239lPjGgcvIlCpLJfgaE=; b=Lrp3Astpuzo/U0OI/bxBNKTmE8EWftrSCNWxO6JjkRwLyfJuaBjzvKW4IyRkbENAln 2IjC4i8pZOpDaFltC/Fg89MOl7P/z5rVRq7Rh6la1rjkpmC5hDqWunXEA/Je5AQzzHb0 lhytz9h4vy5aNikmDaAktxa6e3gWbdgOvm31rIwyDALW/9/yDe4Xww8PR/e1r3EPbRqg NCSSmVcw/1vWN06aSwXtNH4O1r3vjJNdVtmCZwMS3uXDEFn5dSO+euUMptU3x+CYakjY fKiiNmYmGCklpRVKD/Il8o9Kqlowv8n8Y5SRnGPkYxH9z1qymTcebEY1kQai0qbG/zPA 1exA== MIME-Version: 1.0 Received: by 10.220.238.146 with SMTP id ks18mr11941185vcb.58.1358135807443; Sun, 13 Jan 2013 19:56:47 -0800 (PST) Received: by 10.220.174.135 with HTTP; Sun, 13 Jan 2013 19:56:47 -0800 (PST) In-Reply-To: <1358131900.32417.44.camel@revolution.hippie.lan> References: <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu> <20130113053725.GL1410@funkthat.com> <20130113202952.GO1410@funkthat.com> <20130113224800.GS1410@funkthat.com> <50F33B02.6040303@freebsd.org> <1358131900.32417.44.camel@revolution.hippie.lan> Date: Sun, 13 Jan 2013 19:56:47 -0800 Message-ID: Subject: Re: how long to keep support for gcc on x86? From: Peter Wemm To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQngTY1VGDuwKa9S+8IF6Gc7nBGTRTTx5QVLrBacVwTnAcQ2dwoLE6qrklrCRodK5rl0jt1L Cc: Adrian Chadd , Nathan Whitehorn , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2013 03:56:49 -0000 On Sun, Jan 13, 2013 at 6:51 PM, Ian Lepore wrote: > On Sun, 2013-01-13 at 16:58 -0800, Peter Wemm wrote: >> On Sun, Jan 13, 2013 at 3:08 PM, Adrian Chadd wrote: >> > ... ? >> > >> > As an embedded platform, I'd expect that people will want to support >> > any feature which dramatically boosts performance whilst reducing CPU. >> > >> > Also, if Intel decide to keep trying to push low power x86 for mobile >> > applications, rather than ARM, x86 may just make a resurgence in >> > places you once thought were servers. >> > >> > 32 bit x86 isn't legacy and won't be for a long time to come. >> >> Our buildworld environment and embedded $everything isn't well known >> for being embedded friendly. I'd wager that if somebody was trying to >> use an i386 kernel in an embedded device where every last thing >> counted, they'd be using an external toolchain targeted for their >> platform and some very selective cross-building. Compiler of >> $your_choice would be on the table if you were doing external >> compiling, and.. the default in-tree compiler does support AES-NI on >> both i386 and amd64, and the logical other choice (gcc-4.6+ and >> binutils) also does. > > Ummm. Search for "industrial single board computer." They're not rare. > Lots of us build products around them. Some of us use FreeBSD to do so, > with the stock toolchain. I sure hope support for 32 bit x86 isn't > fading away any time soon. I had a quick look. Yes, there were quite a few devices, but I didn't find any 32bit-only that had AES-NI. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV bitcoin:188ZjyYLFJiEheQZw4UtU27e2FMLmuRBUE