Re: [Mingw-w64-public] How to detect which threading model is used with the preprocessor?

Hi Thomas! On Thu, Jun 26, 2014 at 11:55 AM, C. Thomas Stover wrote: > On Thu, 26 Jun 2014 09:12:30 +0200, Etienne Sandré-Chardonnal wrote: >> ... >> Will _GLIBCXX_HAS_GTHREADS work in these cases or is this mingw-only? >> ... > > The macro you reference made me curious. Gthreads (part of glib)

Re: [Mingw-w64-public] LTO status?

I currently use LTO in production code. I and my team have been using LTO since gcc 4.7, although as you say it's more mature in 4.9. We are a small games development house so performance is critical and LTO makes a big difference to our release builds. However, I have also seen a few spurious b

Re: [Mingw-w64-public] Mingw-w64-public Digest, Vol 81, Issue 17

2014-06-26 22:07 GMT+02:00 Etienne Sandré-Chardonnal : > On Thu, 26 Jun 2014 09:51:41 +0200, Ruben Van Boxem wrote: > > The posix threading model enabled toolchains do not interfere or prevent >> the use of Win32 threads. In fact, C++ std::thread is a wrapper of a >> wrapper (GCC's internal gthrea

Re: [Mingw-w64-public] Mingw-w64-public Digest, Vol 81, Issue 17

On Thu, 26 Jun 2014 09:51:41 +0200, Ruben Van Boxem wrote: The posix threading model enabled toolchains do not interfere or prevent > the use of Win32 threads. In fact, C++ std::thread is a wrapper of a > wrapper (GCC's internal gthread) of a wrapper (winpthreads) of Win32 native > threading primi

Re: [Mingw-w64-public] Mingw-w64-public Digest, Vol 81, Issue 17

On Thu, 26 Jun 2014 15:55:59 +, C. Thomas Stover wrote: The macro you reference made me curious. Gthreads (part of glib) written > in C, is a wrapper around pthreads or win32 depending on how it was > built. This allows for a mix of generic code that uses the wrappers and > back-end specific

Re: [Mingw-w64-public] How to detect which threading model is used with the preprocessor?

On Thu, 26 Jun 2014 09:12:30 +0200, Etienne Sandré-Chardonnal wrote: > Hi, > > Is it possible to detect the threading model (win32 / pthreads) with the > preprocessor? > > At least I would like to make the code compile in these two cases > - mingw-w64 with native win32 thread support : use win3

[Mingw-w64-public] [PATCH 0/2] Fix generating *.idl files for IPsec include headers

Hi, > The header is generated from its *.idl though, and the idl needs > fixing accordingly. Sorry, missed that. The two follow-up commits should fix the associated *.idl files as well. Thanks, Martin PS: Please CC me in any reply, I'm not subscribed to the list. -

[Mingw-w64-public] [PATCH 1/2] fwptypes.idl: Remove FWPM_DISPLAY_DATA0 type defintion

After removing it from the header file, remove the definition from the generating .idl file as well. --- mingw-w64-headers/include/fwptypes.idl | 7 --- 1 file changed, 7 deletions(-) diff --git a/mingw-w64-headers/include/fwptypes.idl b/mingw-w64-headers/include/fwptypes.idl index e3cbee5..

[Mingw-w64-public] [PATCH 2/2] iketypes.idl: Remove superfluous #endif

After removing it from the header file, remove the #endif quote from the generating .idl file as well. --- mingw-w64-headers/include/iketypes.idl | 1 - 1 file changed, 1 deletion(-) diff --git a/mingw-w64-headers/include/iketypes.idl b/mingw-w64-headers/include/iketypes.idl index 4dba312..86adf

Re: [Mingw-w64-public] How to detect which threading model is used with the preprocessor?

2014-06-26 9:12 GMT+02:00 Etienne Sandré-Chardonnal : > Hi, > > Is it possible to detect the threading model (win32 / pthreads) with the > preprocessor? > > At least I would like to make the code compile in these two cases > - mingw-w64 with native win32 thread support : use win32 api > - mingw

[Mingw-w64-public] How to detect which threading model is used with the preprocessor?

Hi, Is it possible to detect the threading model (win32 / pthreads) with the preprocessor? At least I would like to make the code compile in these two cases - mingw-w64 with native win32 thread support : use win32 api - mingw-w64 with pthreads or linux gcc : use c++11 Will _GLIBCXX_HAS_GTHREAD