homepage

The 2.44 changes to objimpl.h, especially the "long double" bit, causes numerous warnings on Mac OS X (and possible on other gcc-based platforms). Maybe the suggestion of adding the -Wno-long-double option should be taken, maybe something else should be done (adding a config-based define for the type with the biggest alignment requirement?).
/Users/jack/src/python/Include/objimpl.h:275: warning: use of `long double' type; its size may change in a future release
/Users/jack/src/python/Include/objimpl.h:275: warning: (Long double usage is reported only once for each file.
/Users/jack/src/python/Include/objimpl.h:275: warning: To disable this warning, use -Wno-long-double.)

Logged In: YES 
user_id=31435
Well, since 2.44 consisted entirely of adding the 5-
character string "long " to objimpl.h, I think we can be 
sure that was the cause <wink>.
But "long double" a standard C type, and I don't think a 
compiler has any business warning about using a standard C 
type in a vanilla way. Someone who has access to this 
compiler should fix it, if they care enough to do so. 
That's not me on either count, so I'm unassigning this 
report.

Logged In: YES 
user_id=45365
Added a -Wno-long-double to the CFLAGS (configure.in 1.295, configure 1.285). It turns out MacOSX gcc gives the warning because Mac compilers have traditionally used either 64, 96 or 128 bits for long double, and Apple hasn't decided yet what the final size will be for OSX gcc (and when they change this that will change the compiler ABI).

I reverted this in r61436 to fix issue 1779871. The long double is still
around, but the gcc bundled with OS X 10.4 doesn't warn about it anymore.