From owner-freebsd-numerics@freebsd.org Tue Feb 14 01:53:40 2017 Return-Path: Delivered-To: freebsd-numerics@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 869C0CDDD14 for ; Tue, 14 Feb 2017 01:53:40 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail104.syd.optusnet.com.au (mail104.syd.optusnet.com.au [211.29.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 50CF71657 for ; Tue, 14 Feb 2017 01:53:40 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from besplex.bde.org (c122-106-153-191.carlnfd1.nsw.optusnet.com.au [122.106.153.191]) by mail104.syd.optusnet.com.au (Postfix) with ESMTPS id D037142CC30; Tue, 14 Feb 2017 12:41:15 +1100 (AEDT) Date: Tue, 14 Feb 2017 12:41:14 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Alan Braslau cc: freebsd-numerics@freebsd.org Subject: Re: FreeBSD numerics - cpow() In-Reply-To: <20170213091051.600f91e1@zoo.hsd1.co.comcast.net> Message-ID: <20170214124031.G1263@besplex.bde.org> References: <20170213091051.600f91e1@zoo.hsd1.co.comcast.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.2 cv=BKLDlBYG c=1 sm=1 tr=0 a=Tj3pCpwHnMupdyZSltBt7Q==:117 a=Tj3pCpwHnMupdyZSltBt7Q==:17 a=kj9zAlcOel0A:10 a=WP5Hxxpn-Ad4OME4mSwA:9 a=CjuIK1q_8ugA:10 a=uFNWXhHFHTcA:10 X-BeenThere: freebsd-numerics@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 14 Feb 2017 01:53:40 -0000 On Mon, 13 Feb 2017, Alan Braslau wrote: > What is the current status of getting cpow() implemented in FreeBSD? > > We include ffi (luaffi) in luatex, and the missing cpow() obligates us > to exclude all complex functions (for now) under FreeBSD. No one is working on it AFAIK. Bruce