From owner-freebsd-numerics@FreeBSD.ORG Tue Nov 12 05:20:48 2013 Return-Path: Delivered-To: freebsd-numerics@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 EDDE18B8; Tue, 12 Nov 2013 05:20:48 +0000 (UTC) Received: from zim.MIT.EDU (poofydog.net [198.0.194.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2C283FD1; Tue, 12 Nov 2013 05:20:48 +0000 (UTC) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.7/8.14.7) with ESMTP id rAB2mcDD015182; Sun, 10 Nov 2013 18:48:38 -0800 (PST) (envelope-from das@freebsd.org) Received: (from das@localhost) by zim.MIT.EDU (8.14.7/8.14.7/Submit) id rAB2lrh7015172; Sun, 10 Nov 2013 18:47:53 -0800 (PST) (envelope-from das@freebsd.org) Date: Sun, 10 Nov 2013 18:47:53 -0800 From: David Schultz To: Bruce Evans Subject: Re: MUSL math functions Message-ID: <20131111024753.GA15115@zim.MIT.EDU> References: <20131031133352.GA59918@troutmask.apl.washington.edu> <20131101072032.P1002@besplex.bde.org> <20131108085039.GA1821@zim.MIT.EDU> <15792BD0-C47C-4DCA-A112-D3C54F211E67@FreeBSD.org> <20131111040050.D29424@besplex.bde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131111040050.D29424@besplex.bde.org> Cc: "freebsd-numerics@FreeBSD.org" , David Chisnall , Steve Kargl X-BeenThere: freebsd-numerics@freebsd.org X-Mailman-Version: 2.1.16 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, 12 Nov 2013 05:20:49 -0000 On Mon, Nov 11, 2013, Bruce Evans wrote: > On Sun, 10 Nov 2013, David Chisnall wrote: > > MIPS is also ld128 on most systems, but the fact that there is no 128-bit floating point hardware for MIPS (except in one ASE, where there is one 128-bit floating point accumulator register) makes this quite a silly choice, so it will probably stay ld64. > > Does anyone have it in hardware? Not as far as I know. The format is fairly impractical, for three reasons: 1. Lack of hardware support means it's slow. 2. Given that it's already slow, those who need the extra precision would probably prefer to just use an arbitrary-precision library. 3. People who don't know any better frequently use 'long double' in their code, even when double would suffice. This is okay on x86, but their programs run exceptionally slowly on platforms that use the ld128 format.