From owner-freebsd-arch@FreeBSD.ORG  Fri Jul 12 23:02:05 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 C503F320
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 23:02:05 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com
 [IPv6:2a00:1450:400c:c03::22b])
 by mx1.freebsd.org (Postfix) with ESMTP id 61B8915DB
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 23:02:05 +0000 (UTC)
Received: by mail-we0-f171.google.com with SMTP id m46so8520049wev.16
 for <freebsd-arch@freebsd.org>; Fri, 12 Jul 2013 16:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=6NMyVMeMIUYfPVr5Z51/jstEhRBPXCTX+iDmJtMY3wQ=;
 b=0Gb7rxj01YlsAcICeYnwAZ/dFD2xBY6YXVBntkJ8Dj63LlLT6g9YYwBW8vwfHEaD9e
 kp3c1288KTwYGSN4Lz/Z9wURjcazpuK/yGMomOBDZLCH840kIMXy6H29dzt/QP/SOi/P
 +ViWLJt/tZDCLPK8BoqJvWP8nVMeepNKsPaU2qHw3DCazIhS78k8mf7XKnv8RfE791I4
 gEbLTdzN2hEYMnzwd7DK93aNMvz9/nJhJPn2SRl2gNxAefp6iZNUchKVjbK6kw282Vx+
 gwtEtVppWJrXyCSmYADGL+TDIxyDwzrUoANtNSNhziKqykg6Ur63d8QS+KLdwJfTzWbj
 2tMg==
MIME-Version: 1.0
X-Received: by 10.194.240.201 with SMTP id wc9mr25513406wjc.1.1373670124307;
 Fri, 12 Jul 2013 16:02:04 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.94.132 with HTTP; Fri, 12 Jul 2013 16:02:04 -0700 (PDT)
In-Reply-To: <51E06B85.10109@pix.net>
References: <F79E2F76-A234-499A-ABB7-1ABA62283E9D@FreeBSD.org>
 <51E06B85.10109@pix.net>
Date: Fri, 12 Jul 2013 16:02:04 -0700
X-Google-Sender-Auth: 7OyqyjQf4BhRpoL1n0Jlx4XAc2A
Message-ID: <CAJ-Vmo=HoTRBXnJXeVT7dDW-kHLpQCiB4PFya97P5_5oD5Xx6A@mail.gmail.com>
Subject: Re: Adding a MACHINE_ARCH note
From: Adrian Chadd <adrian@freebsd.org>
To: Kurt Lidl <lidl@pix.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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 <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 23:02:05 -0000

On 12 July 2013 13:48, Kurt Lidl <lidl@pix.net> wrote:
>> 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".

Does this mean that netbooks with only 32 bit CPUs in them won't support NaCl?
(Ie, they're only ever going to generate x32 code, and even 32 bit
machines will still run 64 bit assembly..)


-adrian