From owner-freebsd-numerics@FreeBSD.ORG Thu May 30 20:35:14 2013 Return-Path: Delivered-To: freebsd-numerics@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 74AEE31B; Thu, 30 May 2013 20:35:14 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0]) by mx1.freebsd.org (Postfix) with ESMTP id 4D363640; Thu, 30 May 2013 20:35:14 +0000 (UTC) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.5/8.14.5) with ESMTP id r4UKZCqQ069030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Thu, 30 May 2013 16:35:12 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.5/8.14.5/Submit) id r4UKZCOZ069027; Thu, 30 May 2013 16:35:12 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20903.47104.38977.577307@khavrinen.csail.mit.edu> Date: Thu, 30 May 2013 16:35:12 -0400 From: Garrett Wollman To: Warner Losh Subject: Re: standards/175811: libstdc++ needs complex support in order use C99 In-Reply-To: References: <201302040328.r143SUd3039504@freefall.freebsd.org> <510F306A.6090009@missouri.edu> <20130530064635.GA91597@zim.MIT.EDU> X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 30 May 2013 16:35:12 -0400 (EDT) Cc: freebsd-numerics@freebsd.org, freebsd-standards@freebsd.org X-BeenThere: freebsd-numerics@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of high quality implementation of libm functions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 20:35:14 -0000 < said: > I'm all for getting everything we can into the tree that produces an > answer that's not perfect, but close. What's the error that would be > generated with the naive implementation of > long double tgammal(long double f) { return tgamma(f); } Perhaps we could implement these functions in such a way that they logged a message to inform the user (once per process) that they were using a low-quality implementation. That would allow us to implement these functions without totally losing the incentive to implement them properly, and those users who don't actually call those functions would not have to pay the price of further delay. (This would be a non-conforming implementation, since it would have side effects other than those specified by the standard, but we already fail to conform by not implementing the functions at all, so it wouldn't make things *worse*.) -GAWollman