[libdispatch-dev] lib dispatch worker threads may loop depending on compiler optimization
Antonio Carlos de faria
carlos.faria01 at hotmail.com
Fri Sep 16 16:21:04 PDT 2011
> From: jocke at tbricks.com
> Date: Thu, 15 Sep 2011 14:53:16 +0200
> To: jkh at apple.com
> CC: libdispatch-dev at lists.macosforge.org
> Subject: Re: [libdispatch-dev] lib dispatch worker threads may loop depending on compiler optimization
> On 13 sep 2011, at 10:45, Jordan K. Hubbard wrote:
> On Sep 12, 2011, at 11:06 PM, Joakim Johansson wrote:
> >> 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).
> > Just to chime in with Jean-Daniel - what svn tag of clang did you last test against, if I might ask?
> > It might not be a bad idea to re-test against trunk, if that's possible, since it would at least let you know whether gcc was really a short-term or a medium-term problem.
> Now we retested with trunk:r139788 on Mac OS X 10.7.1 - it still fails, but now we have a bug report with a minimized test case:
> Also, the following case is problematic to get clang working on Solaris, but that is a separate issue:
> (clang/llvm builds out of the box now with gcc, but the resulting compiler can’t build itself due to 5172)
> libdispatch-dev mailing list
> libdispatch-dev at lists.macosforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libdispatch-dev