This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Type of long double on ColdFire
- From: Richard Henderson <rth at redhat dot com>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: ColdFire at lists dot wildrice dot com, gnu-fs-coldfire at codesourcery dot com, gcc at gcc dot gnu dot org
- Date: Thu, 8 Dec 2005 15:40:39 -0800
- Subject: Re: [RFC] Type of long double on ColdFire
- References: <200512081605.47215.paul@codesourcery.com>
On Thu, Dec 08, 2005 at 04:05:46PM +0000, Paul Brook wrote:
> 1) Make long double == double. This is what Arm does, amongst others. This
> pretty much just works and should reduce the amount of support code required.
> Anyone wanting more than IEEE double precision has to use a third party
> bugnum/MP/quad library of which there are several, but no standard ABI.
This would be ok, I guess.
> 2) Choose a sensible format for long double. The obvious candidate is a
> 128-bit PPC/MIPS stye almost-quad precision type implemented with a pair of
> 64-bit doubles.
This is a horrible idea, I think. It's gratuitously incompatible
with other m68k, and most other popular platforms.
> This email is a RFC to try and gauge which of the two options is most useful
> to the ColdFire community. ie. are there significant users that would benefit
> from (2).
I'm not a member of this community though, so I'll be quiet.
r~