Re: [RFC] Type of long double on ColdFire

2005-12-08 Thread Richard Henderson
On Thu, Dec 08, 2005 at 04:05:46PM +, 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 > bugn

Re: [RFC] Type of long double on ColdFire

2005-12-08 Thread Mike Stump
On Dec 8, 2005, at 8:05 AM, Paul Brook wrote: 1) Make long double == double. Eventually the day will come when one want something bigger, then, you have to break abi for this. We did this on darwin, and ick, whatta pain. I think I prefer a hard error for even mentioning long double, as

[RFC] Type of long double on ColdFire

2005-12-08 Thread Paul Brook
We (CodeSourcery) currently working on developing ColdFire targeted GNU toolchains (gcc, etc). Currently gcc nominally uses a 12-byte "extended" precision type for the C "long double" floating point type. This is inherited from the m68k gcc port, but doesn't really make a whole lot of sense for