Re: [Mingw-w64-public] Timer resolution issue

You should use GCC 10.1.1 built by LH_MOUSE https://gcc-mcf.lhmouse.com/ Or GCC 11 by me. https://bitbucket.org/ejsvifq_mabmip/mingw-gcc Sent from Mail for Windows 10 From: Tempelaar E. (E

Re: [Mingw-w64-public] [PATCH 1/6] winpthreads: simplify the USE_VEH_FOR_MSC_SETTHREADNAME check

Hi, Any update on this patchset ? On 2020-04-08 17:13, Steve Lhomme wrote: When compiling with other compilers than MSVC, we always use the code relying on USE_VEH_FOR_MSC_SETTHREADNAME. The __try/__except check code is not modified as it relies on internal MSVC dialect. With MSVC either USE_V

[Mingw-w64-public] Timer resolution issue

In an attempt to upgrade our toolchain (to i.e. GCC 9.3.0) I run into issues with timing of threads. Something that used to work fine with GCC 7.2.0 no longer works as fast as it did when I try to put my thread to sleep for a short amount of time (< 15 msec) According to this: https://stackover

[Mingw-w64-public] [PATCH] dwrite_1.h: Fix build in C mode

Some classes† in the file declare overloaded functions, and this causes a C compiler to fail on module including dwrite_1.h. This commit fixes that. To be consistent on changes I rewrote declaration of all classes/structs in the file, even if one doesn't use overloaded functions. No changes fo