From owner-svn-src-all@freebsd.org Mon May 28 16:59:03 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68FD3F70CF7; Mon, 28 May 2018 16:59:03 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 08F9B7739C; Mon, 28 May 2018 16:59:02 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [IPv6:2a02:c7f:1e13:cf00:da3:9e10:9f00:cd45] (unknown [IPv6:2a02:c7f:1e13:cf00:da3:9e10:9f00:cd45]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id 228F24E774; Mon, 28 May 2018 16:58:54 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Deorbiting i386 From: Andrew Turner In-Reply-To: Date: Mon, 28 May 2018 17:58:52 +0100 Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <201805232218.w4NMIxMA067892@slippy.cwsent.com> <18a87d6d-14af-ef9d-80ff-403039e36692@cs.duke.edu> <20180525003949.GA710@lonesome.com> <05C5BD86-70D0-4B02-AC29-36E68B3602AE@FreeBSD.org> <1A6567CD-5BE8-4E80-A262-00ADB75CF35A@FreeBSD.org> To: Maxim Sobolev X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 16:59:03 -0000 > On 27 May 2018, at 23:15, Maxim Sobolev wrote: >=20 > Well, strip extra 32 bits, use slower memory and busses (extra = decoding logic etc). Voila, you suddenly have platform that can run 99% = of code in wild today with just few hundred mW of power. Try that with = arm32, you would be surprised how many software is technically compiling = and all that, but has some weird runtime issues with either byte order = or unaligned memory accesses. Not even mention performance issues due to = the lack of hand-crafted JITs. If you=E2=80=99re having byte order issues on arm you will have them on = x86 as they are both little endian, and modern arm (last ~10 years) = handles unaligned access. You=E2=80=99ll also find there is a lot of code designed for use on = battery powered Arm CPUs, they are used in almost all mobile phones, = meaning many popular JITs have been ported. Andrew=