Date: Wed, 5 Mar 2008 23:13:33 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Bruce Evans <bde@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/include _types.h Message-ID: <20080305230954.X55190@odysseus.silby.com> In-Reply-To: <200803051121.m25BLE03035426@repoman.freebsd.org> References: <200803051121.m25BLE03035426@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Mar 2008, Bruce Evans wrote: > bde 2008-03-05 11:21:14 UTC > > FreeBSD src repository > > Modified files: > sys/i386/include _types.h > Log: > Change float_t and double_t to long double on i386. All floating point For those of us who are not floating point experts, can you explain a few things? 1) Does this really change every double to a long double in anything compiled? 2) How does this affect ABI compatibility? 3) How does this change the operation of various programs in the ports tree that use floating point, such as mplayer, mpg123, etc. Will this cause different behavior when these apps are used on FreeBSD vs other operating systems? As I've said in the past, I'd really, really, really like to see regression tests for any change to the floating point functions. The types of changes you've been making are not easy to verify just by looking at diffs. Thanks, -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080305230954.X55190>