[Mingw-w64-public] winnt.h:3557:7: error: unknown type name 'PEXCEPTION_ROUTINE'

2013-09-07 Thread Kyle
I'm getting the following error while trying to compile a i686 (32-bit) toolchain using the latest MinGW-w64 sources: i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I/home/kyle/software/mingw-w64/static/source/mingw-w64-svn/trunk/mingw-w64-crt -m32

Re: [Mingw-w64-public] winnt.h:3557:7: error: unknown type name 'PEXCEPTION_ROUTINE'

2013-09-07 Thread Kai Tietz
Yes, this is a 32-bit only regression. Issue is fixed at rev 6226. Thanks for reporting. Kai -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous

Re: [Mingw-w64-public] The API supported by g++11_64bit

2013-09-07 Thread Óscar Fuentes
Incongruous incongru...@outlook.com writes: OKay? Code Snip #include memory //share_ptr std::shared_ptrabc::someClass apx; //--Does not work Error g++-c -g -I/c/abc -I/c/abc/gui/msg/ -MMD -MP -MF build/Debug/MinGW64-Windows/_ext/348948719/MyClass.o.d -o

Re: [Mingw-w64-public] [Patch] intrinsics

2013-09-07 Thread Jacek Caban
On 09/07/13 03:20, JonY wrote: On 9/7/2013 08:44, dw wrote: However, if that's not acceptable, perhaps there is an alternative. If the requirement I'm violating here is simply that these specific functions must be able to support not being inlined, then I believe simply changing them from

[Mingw-w64-public] what's the diff b/w -std=c++11 and -std=gnu++11

2013-09-07 Thread Incongruous
I am trying to figure out the difference between -std=c++11 and -std=gnu++11. According to: http://gcc.gnu.org/gcc-4.8/cxx0x_status.html “...with the -std=c++11 or -std=gnu++11 compiler options; the former disables GNU extensions.”, my question is, what is it that std=c++11 disables? In other

Re: [Mingw-w64-public] what's the diff b/w -std=c++11 and -std=gnu++11

2013-09-07 Thread Ruben Van Boxem
Op 7-sep.-2013 17:08 schreef Incongruous incongru...@outlook.com het volgende: I am trying to figure out the difference between -std=c++11 and -std=gnu++11. According to: http://gcc.gnu.org/gcc-4.8/cxx0x_status.html “...with the -std=c++11 or -std=gnu++11 compiler options; the former disables

Re: [Mingw-w64-public] mingw-w64 v3 release calling for testers

2013-09-07 Thread Tony Theodore
On 07/09/2013, at 3:25 AM, NightStrike nightstr...@gmail.com wrote: On Fri, Sep 6, 2013 at 11:25 AM, Erik van Pienbroek Before I kick off another test mass rebuild I would like to know whether there are still any winpthreads changes pending. Previous test mass rebuilds have shown that

Re: [Mingw-w64-public] mingw-w64 v3 release calling for testers

2013-09-07 Thread JonY
On 9/8/2013 10:48, Tony Theodore wrote: On 07/09/2013, at 3:25 AM, NightStrike wrote: On Fri, Sep 6, 2013 at 11:25 AM, Erik van Pienbroek Before I kick off another test mass rebuild I would like to know whether there are still any winpthreads changes pending. Previous test mass rebuilds

Re: [Mingw-w64-public] mingw-w64 v3 release calling for testers

2013-09-07 Thread Tony Theodore
On 08/09/2013, at 12:48 PM, Tony Theodore tony.theod...@gmail.com wrote: On 07/09/2013, at 3:25 AM, NightStrike nightstr...@gmail.com wrote: I'm at least trying to get the winpthreads build fixes in that you asked for On r6232, I'm seeing these build errors in winpthreads itself: