Date: Mon, 17 Feb 2003 22:48:40 -0500 From: Mike Barcroft <mike@FreeBSD.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Kris Kennaway <kris@obsecurity.org>, standards@freebsd.org Subject: Re: -fno-builtin world breaks in gperf Message-ID: <20030217224840.L74149@espresso.bsdmike.org> In-Reply-To: <20030217193655.I74149@espresso.bsdmike.org>; from mike@FreeBSD.org on Mon, Feb 17, 2003 at 07:36:55PM -0500 References: <xzp1y2755jc.fsf@flood.ping.uio.no> <20030217213405.GB71679@rot13.obsecurity.org> <xzp8ywezc7z.fsf@flood.ping.uio.no> <20030217193655.I74149@espresso.bsdmike.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Barcroft <mike@FreeBSD.org> writes: > Dag-Erling Smorgrav <des@ofug.org> writes: > > Kris Kennaway <kris@obsecurity.org> writes: > > > On Mon, Feb 17, 2003 at 03:46:15PM +0100, Dag-Erling Smorgrav wrote: > > > > Our libm doesn't seem to support long double at all, yet our libstdc++ > > > > requires long double support. > > > I pointed this out a while ago..looks like no-one did anything about > > > it yet. > > > > I've looked at it, and it looks Hard[tm]. The four architectures I > > tested (alpha, ia32, ia64, sparc64) had four different representations > > for long double: > [...] > > You might want to take a look at the fpclassify() implementation. It > doesn't look like your findings are correct. Specifically, see the > bitfield layouts in _fpmath.h. > > IIRC, long doubles are as follows: [...] > - ia64 IEEE quad (128-bit) format Oops, this is actually just a double-extended 80-bit, but aligned to 16-bytes. I'm in the progress of testing a fix for _fpmath.h. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030217224840.L74149>