在 2020/5/18 15:15, Tempelaar E. (Erik) 写道:
> I've been searching the web for answers but I'm a bit lost.
> What can explain the difference in behaviour of the two msys2 environments on
> my system?
>
> Is it a regression in Windows 10 1803, as discussed in this PR with a
> workaround to force th
rom: Tempelaar E. (Erik)<mailto:erik.tempel...@vanoord.com>
Sent: Monday, May 18, 2020 06:51
To:
'mingw-w64-public@lists.sourceforge.net'<mailto:mingw-w64-public@lists.sourceforge.net>
Subject: [Mingw-w64-public] Timer resolution issue
In an attempt to upgrade our toolchain (to
Tempelaar E. (Erik)<mailto:erik.tempel...@vanoord.com>
Sent: Monday, May 18, 2020 06:51
To:
'mingw-w64-public@lists.sourceforge.net'<mailto:mingw-w64-public@lists.sourceforge.net>
Subject: [Mingw-w64-public] Timer resolution issue
In an attempt to upgrade our toolchain (to
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
