From owner-freebsd-current@FreeBSD.ORG Fri Jun 1 15:22:53 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 138541065676 for ; Fri, 1 Jun 2012 15:22:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id DB0298FC19 for ; Fri, 1 Jun 2012 15:22:52 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 44B20B962; Fri, 1 Jun 2012 11:22:52 -0400 (EDT) From: John Baldwin To: Eitan Adler Date: Fri, 1 Jun 2012 10:29:13 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: <4FC30090.4070003@gwdg.de> <201205311145.15454.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201206011029.13865.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 01 Jun 2012 11:22:52 -0400 (EDT) Cc: freebsd-current@freebsd.org, Peter Jeremy , Steve Kargl Subject: Re: Use of C99 extra long double math functions after r236148 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 15:22:53 -0000 On Friday, June 01, 2012 1:55:10 am Eitan Adler wrote: > On 31 May 2012 08:45, John Baldwin wrote: > > I do think we should provide something in ports as an interim solution. > > There are other 3rd party applications looking to drop FreeBSD support > > because we are missing APIs that almost all other OS's have. I'm fine > > if the interim lives in ports and that we don't import substandard > > routines into the base. I would even be fine with calling it > > /usr/local/lib/libm_inaccurate.so. However, I do think we need an option. > > Do we have a wiki page listing the functions in libm we are missing? > Having some kind of place to track progress and figure out what > exactly is needed is the first step to getting these APIs into shape. > > Also, are there BSD licensed naive implementations of these functions > we can use? Would it be okay to have slow, but accurate versions of > these functions as a stopgap? Peter Jeremy more or less has a stopgap already ready judging by the comments in the thread thus far. -- John Baldwin