libm

Callum Lerwick seg at haxxed.com
Tue Jul 11 21:26:26 UTC 2006


On Tue, 2006-07-11 at 22:02 +0200, Rudi Chiarito wrote:
> Is there a reason why under 32bit FC5 and 64bit FC3 the library
> references libm, while it doesn't under 64bit FC5? It doesn't look like
> the most predictable behaviour to me. Which of the two is considered
> more proper?

Could this be compiler optimizations? GCC can replace libm calls with
inline assembly. Since x86_64 isn't saddled with i[345]86 compatibility
(3DNow, SSE and SSE2 are guaranteed to be available) it can do a lot
more of these optimizations than a generic i386 build can. Newer GCCs
might not even be bothering to link in libm if it has been able to
replace all calls with inline instructions.

Or maybe fftw itself is switching to x86_64 assembly. It appears recent
versions do have x86_64 assembly optimizations.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20060711/9f2256c3/attachment.sig>


More information about the fedora-devel-list mailing list