[libdispatch-dev] lib dispatch worker threads may loop depending on compiler optimization
devlists at shadowlab.org
Tue Sep 13 01:18:43 PDT 2011
Le 13 sept. 2011 à 08:06, Joakim Johansson a écrit :
> On 12 sep 2011, at 21:57, Jordan K. Hubbard wrote:
>> Seeing as how gcc (outside of Apple) doesn't even support blocks, which I think we all agree are somewhat fundamental to GCD's ease-of-use, is there any real benefit to trying to grapple with gcc build issues in any case? I have a hard time seeing the point of creating a build of libdispatch which only supports the _f() variants, in other words, and if the user is already essentially forced to use clang in order to truly benefit from libdispatch, then why not make the bootstrapping of clang on each given target platform a prerequisite? (I googled for "clang for windows" and got a fair number of hits, btw, though I don't know how fully baked that port is yet). Just a thought!
> I definitely agree that blocks are very nice (as is clang, which I hope that we will be able to use pending ability to build our C++ code, which was still lacking last time we tested).
You should definitively give it a new try. C++ has greatly improved. Last build supports most if not all of c++98, and a bunch of C++0x features too.
If clang failed to build your c++ code, you should fill bug reports.
More information about the libdispatch-dev