[ColdFire 14/63] Make "long double" the same as "double" on ColdFire

Jeffrey Law law@redhat.com
Wed Jan 10 18:35:00 GMT 2007


On Wed, 2007-01-10 at 11:01 +0000, Richard Sandiford wrote:
> When we (CodeSourcery) polled ColdFire folks, there seemed to be
> general agreement that "long double" should be the same as "double"
> on ColdFire.  There doesn't seem much point emulating the m68k
> XFmode format.
> 
> This patch adjusts LONG_DOUBLE_TYPE_SIZE accordingly.  It's an ABI
> change for all ColdFire targets.
> 
> Richard
> 
> 
> gcc/
> 200x-xx-xx  Julian Brown  <julian@codesourcery.com>
> 
> 	* config/m68k/m68k.h (LONG_DOUBLE_TYPE_SIZE): Make 64-bit on ColdFire.
> 	(LIBGCC2_LONG_DOUBLE_TYPE_SIZE): Likewise. 
> 	* config/m68k/netbsd-elf.h (LIBGCC2_LONG_DOUBLE_TYPE_SIZE): Undefine
> 	before redefining.
Where/how do we document ABI changes for releases?  Even if the coldfire
users are in agreement we need a reasonable way to notify them when the
ABI has changed.

It also seems to me that if this can be configurable, then it probably
should be given that we're changing the current behavior.  Even if
you've polled many coldfire users, there's a reasonable chance there's
someone out there you missed that's using 128bit long doubles.

Let's table this one temporarily.

jeff




More information about the Gcc-patches mailing list