From owner-freebsd-ppc@FreeBSD.ORG Mon Jul 19 00:33:07 2004 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27DF616A4CE for ; Mon, 19 Jul 2004 00:33:07 +0000 (GMT) Received: from liberty.onthenet.com.au (liberty.OntheNet.com.au [203.22.124.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 942E743D41 for ; Mon, 19 Jul 2004 00:33:06 +0000 (GMT) (envelope-from grehan@freebsd.org) Received: from freebsd.org (CPE-25-247.dsl.onthenet.net [203.144.25.247]) i6J0WunP020358; Mon, 19 Jul 2004 10:32:56 +1000 (EST) (envelope-from grehan@freebsd.org) Message-ID: <40FB1851.3030305@freebsd.org> Date: Mon, 19 Jul 2004 10:39:45 +1000 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <16634.60434.732990.437652@grasshopper.cs.duke.edu> In-Reply-To: <16634.60434.732990.437652@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-ppc@freebsd.org Subject: Re: long doubles? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 00:33:07 -0000 > According to a printf of sizeof(long double), the size of a long > double is 8 bytes, the same as a double. However, according to > sys/powerpc/include/float.h, LDBL_MANT_DIG == 113.. I don't know a > lot about floating point, but I'm not sure this is possible. ;) > > If long doubles are 8 bytes (and they are on MacOSX, so that's a good > sign), then shouldn't the LDBL_* constants be the same as the DBL* > constants from float.h? (they are on MacOSX) Yeh, I'm not too sure about this. The SVR4 ABI defines long doubles as 128 bits, and there is a GCC config knob to enable this. I'd promised David Schultz that'd I would look at fixing this, but haven't gotten around to it yet. later, Peter.