Lib change leads to larger executables

[Sean Kelly]

Walter Bright wrote:
> Frits van Bommel wrote:
> 
>> If so, the obvious workaround would be to tell it to only use one thread.
>> If not, why does multicore matter?
> 
> The way mutexes are done for multi core is different than for single 
> core. I think optlink multithreads correctly only for single core machines.

Assuming you're talking about cores that don't share a cache (ie. "real" 
SMP) then it's possible optlink id just doing its own synchronization by 
manipulating variables.  Fixing it might be as easy as sticking a lock 
prefix in the right locations (long shot, I know).


Sean