From owner-freebsd-threads@FreeBSD.ORG Mon Dec 19 17:56:12 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 BAE081065670; Mon, 19 Dec 2011 17:56:12 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 711228FC18; Mon, 19 Dec 2011 17:56:12 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Rch9e-000733-Rp>; Mon, 19 Dec 2011 18:37:38 +0100 Received: from e178006011.adsl.alicedsl.de ([85.178.6.11] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Rch9e-0007oE-ND>; Mon, 19 Dec 2011 18:37:38 +0100 Message-ID: <4EEF765D.4090300@zedat.fu-berlin.de> Date: Mon, 19 Dec 2011 18:37:33 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111109 Thunderbird/8.0 MIME-Version: 1.0 To: Warner Losh References: <58923.1324292241@critter.freebsd.dk> In-Reply-To: X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD4679509587AA80EFD2E8B74" X-Originating-IP: 85.178.6.11 Cc: threads@freebsd.org, Poul-Henning Kamp , 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:56:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD4679509587AA80EFD2E8B74 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 12/19/11 18:09, Warner Losh wrote: >=20 > On Dec 19, 2011, at 3:57 AM, Poul-Henning Kamp wrote: >=20 >> In message <201112191152.22907.tijl@coosemans.org>, Tijl Coosemans wri= tes: >> >>>> Big/Little Endian API ? >>>> >>>> Naah, nobody moves binary data between computers. >>> >>> Yes, but rather than having the programmer remember when to swap byte= s, >>> it would be better if he could just declare a variable big/little >>> endian and have the compiler figure it out. >> >> You'd think so, wouldn't you ? >=20 > Intel has a compiler that allows one to declare things are big or littl= e 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... >=20 > Linux marks things as beXX or leXX and uses static analysis to prevent = mixing. >=20 > There's a lot of prior art for the committee to choose from. >=20 > Warner >=20 A silly question: How is the other BSD sibbling, NetBSD, dealing with such things? NetBSD is supposed to run on a trmendous variety of hardware, even a mixture of bigendian and littleenddian and I'm quite sure they must have overcome this probleme anyway. Regrads, Oliver --------------enigD4679509587AA80EFD2E8B74 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO73ZiAAoJEOgBcD7A/5N8Yh4IALIrJvxbQWKmE1/SmOqDz84c WyBoUP6O3Rj816VFXM17Mda/YTG3+L11hYIVqIo/tKZO4knyj11IZ2nZUoiNfc9v PaULHHEVBNw7cNOa/fLUiV7H78dUL7galbEKvhMgKrT9Nbzh06UxlUZmOCZlhZGX 3PvG95m9STJb0Ex2UJnUPim/NmoNDvTOxB8mZjwSfjU89A/nk5a23SlOdsRNFJka XCjWejy0B9CMHGOWMSW/eJ46ePrM6gxpoIDA4vGmIaOlg7jGc7umi1e4dunCMZgY Xbl4gOhixbqaybXrvttRkrWENaA+6uqV5APY17hytK8Tk3sa0PgJQ20DNChrNzA= =FZfG -----END PGP SIGNATURE----- --------------enigD4679509587AA80EFD2E8B74--