[Gecode] Found problem with dynamic linking on Windows and gcc

Christian Schulte schulte at imit.kth.se
Tue May 18 16:03:49 CEST 2004


The incredible slowdown is due to the fact that gcc wraps any access to an
exported memory location into a procedure call! Tada, guess what? The magic
Space::cur which is used very often always costs a procedure call.

What I can see is that gcc is ABSOLUTELY INCAPABLE of building DLLs under
Windows. Let's just forget about it. Not to bad after MSVC is freely
available.

On the other hand even static linking with autoconf shows the same problem.
What's going on there?

Christian

--
Christian Schulte, http://www.imit.kth.se/~schulte/ 




More information about the gecode-users mailing list