Date: Mon, 19 Dec 2011 18:46:24 +0100 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Warner Losh <imp@bsdimp.com> Cc: threads@freebsd.org, Poul-Henning Kamp <phk@phk.freebsd.dk>, Tijl Coosemans <tijl@coosemans.org>, freebsd-arch@freebsd.org Subject: Re: [Patch] C1X threading support Message-ID: <20111219174624.GA13576@onelab2.iet.unipi.it> In-Reply-To: <AC4BCD04-6555-4AD1-BBCD-3C706852ECCF@bsdimp.com> References: <58923.1324292241@critter.freebsd.dk> <AC4BCD04-6555-4AD1-BBCD-3C706852ECCF@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 19, 2011 at 10:09:53AM -0700, Warner Losh wrote: > > On Dec 19, 2011, at 3:57 AM, Poul-Henning Kamp wrote: > > > In message <201112191152.22907.tijl@coosemans.org>, Tijl Coosemans writes: > > > >>> Big/Little Endian API ? > >>> > >>> Naah, nobody moves binary data between computers. > >> > >> 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. > > > > 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. and that would be the definition of a blacklist, right ? :) cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111219174624.GA13576>