[libdispatch-dev] lib dispatch worker threads may loop depending on compiler optimization

Joakim Johansson jocke at tbricks.com
Thu Sep 15 08:31:30 PDT 2011

I do think it is a possibility - we would need to investigate it, we already have a dual-compiler toolchain (GCC + Oracle / Sun Studio) - I’d prefer to be able to switch the GCC part -> clang if possible (or both of those…).

Clang does build libdispatch fine on Solaris, but we haven’t done as extensive testing with it (yet) as we hoped to get C++ up and running as well…

Will discuss it offline a bit...


On 15 sep 2011, at 16:00, Mark Heily wrote:

> On Sep 13, 2011, at 2:06 AM, Joakim Johansson <jocke at tbricks.com> wrote:
>> (for toolchain reasons, we are building the final cut with gcc) 
> Would it be reasonable to use clang to build libdispatch.so while continuing to use GCC to build the rest of your application? That should prevent the GCC 4.5.1 bug from biting you. 
> Sent from my iPhone

More information about the libdispatch-dev mailing list