From owner-svn-src-all@FreeBSD.ORG Wed Apr 2 18:58:13 2014 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C75C019A; Wed, 2 Apr 2014 18:58:13 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F4B5BCB; Wed, 2 Apr 2014 18:58:13 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s32Iw9qD057812 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Apr 2014 18:58:10 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: svn commit: r264042 - in head: include lib/libc/gen lib/libc/include lib/libc/stdlib From: David Chisnall In-Reply-To: <20140402172445.GQ21331@kib.kiev.ua> Date: Wed, 2 Apr 2014 19:58:03 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <743556FF-1473-4795-8419-80A8A3D22D13@FreeBSD.org> References: <201404021607.s32G7mhw051355@svn.freebsd.org> <20140402161845.GP21331@kib.kiev.ua> <76A3F92F-18CB-4A9A-8CF5-3A86035C55BB@FreeBSD.org> <20140402172445.GQ21331@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1874) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 02 Apr 2014 18:58:13 -0000 On 2 Apr 2014, at 18:24, Konstantin Belousov = wrote: > It does, I read it. Read the code again. Or even just read the comments. In particular the = blocks_abi.h file contains a detailed description of why the rest of = what you say is wrong. > Now libc depends on the non-standard ABI Not true, the ABI is documented and is as standard as the C++ ABI. We = have code in ports and in the base system that relies on this ABI = already. > of non-standard C extension, The extension is non-standard, however (if you'd read the code, or the = comments in the code you'd already know that) the code in libc does not = require this extension to exist. > implemented by only one compiler. Actually, by two, both of which are in the base system. Well, three if = you count Apple-GCC as different from FSF-GCC. Oh, and a couple of = proprietary compilers. All of which are only required for *callers* of = these functions. libc itself still builds correctly (and is tested = building) with compilers that don't support blocks. If you have helpful comments, then I suggest you try to phrase them in a = less confrontational tone. David