[libdispatch-dev] lib dispatch worker threads may loop depending on compiler optimization
Jordan K. Hubbard
jkh at apple.com
Tue Sep 13 11:48:57 PDT 2011
On Sep 13, 2011, at 3:39 AM, Joakim Johansson wrote:
> The only problem of not doing ‘a’ (workaround in the GCD source base), is that having a gcc-kludge train would of course work for us internally, but it would still make GCD less accessible if one is willing to live with the subset of functionality provided by gcc - I can see that it is not obvious whether the FSF even views this as a bug (Paolo started the discussion at http://gcc.gnu.org/ml/gcc/2011-09/msg00088.html which is still ongoing…)
A fair point, though I'm still not sure how big the "community" of gcc-4.5.1+libdispatch users truly is. If there are only, say, 4 of you then you can at just pass the patch around at your next user group meeting. ;) That said (and thanks for the pointer to the discussion thread on the gcc lists), I'm seeing more folks in the gcc discussion arguing for treating this as an optimization barrier than not, so maybe the gcc folks WILL make the change and the worst that will happen is you have to wait for gcc-4.5.3 or something. Perhaps we should give the discussion another week or so to play out and then see where things are?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libdispatch-dev