[Bug other/60336] New: va_start corrupts 6-th argument in case of empty type used before the format string

2014-02-25 Thread ahanins at gmail dot com
Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: ahanins at gmail dot com Created attachment 32208 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32208action=edit va_list corruption simple example The code

[Bug libstdc++/59807] mutex misses destructor if non-function call initialization is used

2014-01-29 Thread ahanins at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59807 --- Comment #4 from Andrey H. ahanins at gmail dot com --- Thanks Jonathan, I followed your suggestion regarding os_defines.h, recompiled the whole mingw-w64 toolchain and can confirm that it helps. But doesn't it meant that it should be fixed

[Bug libstdc++/59807] mutex misses destructor if non-function call initialization is used

2014-01-29 Thread ahanins at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59807 --- Comment #7 from Andrey H. ahanins at gmail dot com --- Kai, so what would be the fix? IMHO, this bug is quite a show stopper for C++11 threading in Mingw-w64, so maybe it worth to create a temporary patch for Mingw-w64 compilation

[Bug libstdc++/59807] New: mutex misses destructor if non-function call initialization is used

2014-01-14 Thread ahanins at gmail dot com
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ahanins at gmail dot com Hi, Follow up to https://sourceforge.net/p/mingw-w64/bugs/376/ This is related to GTHR interface to pthread. C++11 __mutex_base class does

[Bug libstdc++/59807] mutex misses destructor if non-function call initialization is used

2014-01-14 Thread ahanins at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59807 --- Comment #1 from Andrey H. ahanins at gmail dot com --- Simplest code which leaks handles on Windows: for(;;) { std::mutex op_mutex; op_mutex.lock(); op_mutex.unlock(); }