Christian Anthon wrote: > Hi all, > > I'm considering to remove the non-threaded code. The threaded code > should be able to run without threads with minor adjustments (replacing > thread-safe operations with equivalent unsafe ones or NULL operations as > appropriate), and we wouldn't have two sets of code to keep working at > the same time. There may still be a small time-penalty involved. Anybody > with a strong opinion against this?
Hi! I actually usually compile without thread support. I feel it's safer and is more stable, and therefore prefer to compile without threads. I can also see that my own builds, without thread support, is considerably faster (in terms of eval/sec) than a single threaded build supporting threads. I therefore believes the thread code adds some overhead. The numbers in evals/sec My own non-thread build: ~56600 eval/sec MaX build single thread: ~48100 eval/sec Of course I'm not convinced that the eval speed test is a fair test in this context, however it is an indicator that there is some overhead involved. I can really see the benefit of having only one code to work at, but I would still love to be able to compile without threads. -Øystein
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
