From: Gabriel D. R. <gd...@in...> - 2012-05-09 19:45:41
|
On Wed, May 9, 2012 at 2:30 PM, K. Frank <kfr...@gm...> wrote: > Hi Gaby! > > On Wed, May 9, 2012 at 3:08 PM, Gabriel Dos Reis > <gd...@in...> wrote: >> On Wed, May 9, 2012 at 2:06 PM, K. Frank <kfr...@gm...> wrote: >> >>> However, as noted in my previous post, I have happily done some >>> (limited) windows-api threading programming with Ruben's build >>> (and also did the windows-api threading programming necessary >>> to implement <thread>), all, I guess, with a gcc build built using >>> --enable-threads=posix, so what then does --enable-threads=win32 >>> actually do? >> >> See TDM's build (which is --enable-threads=win32) > > I've used a couple of TDM's builds in the past (but I'm not sure I > ever used it with threading, unless maybe a few simple test > programs with Qt's QThread, and such). But I haven't noticed > any difference (other than, I would suspect, pthreads not working). > > So what does --enable-threads=win32 vs. --enable-threads=posix > actually do? > >> -- Gaby > > Thanks. > > > K. Frank win32 is the MS Win32 threading model. If that is the default of the compiler, I have a guarantee that I can mix with Win32 threading semantics; otherwise, I don't. Multithreading programming is sufficiently complicated that we don't want to make confuse them just on anedoctical trial. See also http://gcc.gnu.org/viewcvs/trunk/libgcc/config/i386/gthr-win32.h?view=markup http://gcc.gnu.org/viewcvs/trunk/libgcc/config/i386/gthr-win32.c?revision=184997&view=markup -- Gaby |