[C++-sig] Loading Boost.Python made bindings is horribly slow?

Niall Douglas s_sourceforge at nedprod.com
Fri Apr 2 18:55:27 CEST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

With GCC v3.4 from CVS, I finally have build time down to only nine 
hours now rather than the 20+ it was with GCC v3.3. However, when 
loading the bindings into python on Linux v2.4 kernel it takes well 
over six minutes.

Is anyone else having this problem? I don't think it's BPL's fault 
really as on Windows it only takes a second or two so I'm guessing 
it's the dynamic linker. I'd imagine that that prebinding linkage 
feature of newer Linuces will fix this problem - in the meantime, any 
suggestions?

(Here's a thought - GCC outputs far too many symbols into the public 
ELF table - if GCC had a dllexport/dllimport mechanism like on 
Windows, the amount of symbols needing to be linked could be reduced 
very significantly indeed. As it so happens, someone submitted a 
patch to enable per-class symbol visibility specifications using the 
same syntax as MSVC, it just needs extending to use a command line 
argument specified default so you can mark everything default hidden. 
If people here think this a good idea, I may try tackling it).

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBQG2bA8EcvDLFGKbPEQKACQCffwTwb5rzU0ikzQ3aWATWRKHirmEAoJez
fuxMMJ25M6rhVO6No/2o4OKS
=CyW3
-----END PGP SIGNATURE-----




More information about the Cplusplus-sig mailing list