From owner-freebsd-threads@FreeBSD.ORG Mon Dec 19 17:19:23 2011 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 371171065672; Mon, 19 Dec 2011 17:19:23 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id E7F228FC12; Mon, 19 Dec 2011 17:19:22 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pBJHA0NJ049289 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 19 Dec 2011 10:10:02 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <58923.1324292241@critter.freebsd.dk> Date: Mon, 19 Dec 2011 10:09:53 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <58923.1324292241@critter.freebsd.dk> To: "Poul-Henning Kamp" X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 19 Dec 2011 10:10:03 -0700 (MST) Cc: threads@freebsd.org, Tijl Coosemans , freebsd-arch@freebsd.org Subject: Re: [Patch] C1X threading support X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 17:19:23 -0000 On Dec 19, 2011, at 3:57 AM, Poul-Henning Kamp wrote: > In message <201112191152.22907.tijl@coosemans.org>, Tijl Coosemans = writes: >=20 >>> Big/Little Endian API ? >>>=20 >>> Naah, nobody moves binary data between computers. >>=20 >> Yes, but rather than having the programmer remember when to swap = bytes, >> it would be better if he could just declare a variable big/little >> endian and have the compiler figure it out. >=20 > You'd think so, wouldn't you ? Intel has a compiler that allows one to declare things are big or little = endian and then things work. A certain large router vendor used it to = port its software that was big endian only at a very deep layer to Intel = x86... Linux marks things as beXX or leXX and uses static analysis to prevent = mixing. There's a lot of prior art for the committee to choose from. Warner