From owner-freebsd-threads@FreeBSD.ORG Sat Dec 17 21:22:01 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 E4126106567A; Sat, 17 Dec 2011 21:22:01 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id A03678FC12; Sat, 17 Dec 2011 21:22:01 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 8377F5DAA; Sat, 17 Dec 2011 21:02:17 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id pBHL2HRE085478; Sat, 17 Dec 2011 21:02:17 GMT (envelope-from phk@phk.freebsd.dk) To: Kostik Belousov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 17 Dec 2011 00:31:26 +0200." <20111216223126.GX50300@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 17 Dec 2011 21:02:17 +0000 Message-ID: <85477.1324155737@critter.freebsd.dk> Cc: arch@freebsd.org, Ed Schouten , threads@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: Sat, 17 Dec 2011 21:22:02 -0000 In message <20111216223126.GX50300@deviant.kiev.zoral.com.ua>, Kostik Belousov writes: >> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf >BTW, it looks not very useful to add a bunch of threading functions >without at least trying to specify the memory model. I have never fully understood what goal these sequential obesity-binges from ISO-C serve. Structure packing ? Nahh, nobody uses that. Big/Little Endian API ? Naah, nobody moves binary data between computers. Ohhh, but I know: Lets make a rival to the POSIX threads, we can do it much better and slightly incompatible, big market there I'm sure. What ? A "assert mutex is held" facility ? Why would you want that ? Just write perfect code to begin with! Bang! Bang! Bang! &c &c... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.