From owner-freebsd-arch@FreeBSD.ORG  Fri Jul 12 20:48:07 2013
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 0E5F240D
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 20:48:07 +0000 (UTC)
 (envelope-from lidl@pix.net)
Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c])
 by mx1.freebsd.org (Postfix) with ESMTP id DDAB91E13
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 20:48:06 +0000 (UTC)
Received: from torb.pix.net (torb.pix.net
 [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0)
 by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r6CKm5w4061878
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 16:48:05 -0400 (EDT)
 (envelope-from lidl@pix.net)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.8 at mail.pix.net
Message-ID: <51E06B85.10109@pix.net>
Date: Fri, 12 Jul 2013 16:48:05 -0400
From: Kurt Lidl <lidl@pix.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: freebsd-arch@freebsd.org
Subject: Re: Adding a MACHINE_ARCH note
References: <F79E2F76-A234-499A-ABB7-1ABA62283E9D@FreeBSD.org>
In-Reply-To: <F79E2F76-A234-499A-ABB7-1ABA62283E9D@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 12 Jul 2013 20:48:07 -0000

> On Jul 10, 2013, at 03:08, Peter Wemm <peter at wemm.org> wrote:
>> On Tue, Jul 9, 2013 at 5:56 PM, Adrian Chadd <adrian at freebsd.org> wrote:
>>> ... boy I'd like to see this particular x86 hiccup fixed before this
>>> stuff is mainstream.
>>
>> I'm not entirely sure how much support there is behind "x32".  I don't
>> know if its much more than an academic curiosity or if there's real
>> demand for it.
>
> It seems to be driven by Intel and Google.  The idea is that for some
> applications (or maybe even most :), an ILP32 model will perform better.

I believe that Google's NaCl (native client) plugins for Chrome all use
the "x32" ABI.  The NaCl stuff uses this, along with a "safe" code
generation path to implement part of the sandboxing for Chrome plugins.

Ultimately, to have a fully functioning Chrome (with plugins) on amd64
hosts, we'll want to support "x32".

-Kurt