Date: Fri, 25 Oct 2002 01:05:41 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: rittle@latour.rsch.comm.mot.com Cc: current@FreeBSD.ORG Subject: Re: Lack of real long double support Message-ID: <20021025.010541.74072638.imp@bsdimp.com> In-Reply-To: <20021025.004342.06455314.imp@bsdimp.com> References: <20021023123653.A39814@espresso.q9media.com> <200210240833.g9O8XB1W033884@latour.rsch.comm.mot.com> <20021025.004342.06455314.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20021025.004342.06455314.imp@bsdimp.com>
"M. Warner Losh" <imp@bsdimp.com> writes:
: : Anyways, two questions for FreeBSD maintainers. How should gcc, as
: : provided from the FSF, describe the long double FP format for
: : FreeBSD/i386 4.x? Shall we assume that no changes for FreeBSD 5.x
: : will occur?
:
: No. You should assume that for i386, at least, that long double will
: have the right LDBL_ constants. I've had them in my local tree for
: about 3 months now and just haven't found the time to commit to
: -current. I'll find the time right now.
I've committed the fix to the tree. NetBSD uses these numbers, and
I've been using these numbers on a large number of systems that we
maintain at timing solutions (they were added to our local tree prior
to the 4.5 release, and we've built hundreds of ports since then w/o
any issues). I've had them in my own personal p4 tree for 3 months
with similar results.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021025.010541.74072638.imp>