On Wed, May 9, 2012 at 12:04 PM, K. Frank <[email protected]> wrote: > > Personally, as mentioned above, I am quite happy with the winpthreads > implementation of <thread>, as made available in Ruben's build. > > Please, let's have mingw-w64 (and mingw) users chime in. Do folks > prefer one approach (native vs. pthreads) to implementing <thread> > to the other? Is there enough interest in both approaches that it > makes sense to take away manpower from other issues to develop > and support both? >
My druthers leans toward native. The Windows pthreads becomes a wrapper between POSIX and native so there is some loss of CPU resource by using it. > For those who haven't tried it yet, I heartily recommend Ruben's > <thread>-enabled build (that is based on winpthreads under the > hood). I have tested it and been using it some, and I haven't > found any problems with it yet. I have yet to give it a go myself so can't compare anything. Are there metrics using one versus another method? -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
