https://bugs.winehq.org/show_bug.cgi?id=38272
--- Comment #13 from Nikolay Sivov bunglehead@gmail.com --- (In reply to leonbogaert+winehq from comment #12)
Created attachment 51105 [details] Alex' go program as binary
I've attached the program Alex' mentioned as windows binary.
Thank you. With current Wine it gives me:
--- freq=10000000 c1=20212930054540 c2=20212940066008 expected to sleep 1000 milliseconds, but slept for 1001 ---
On Windows 7 installation it's valid as well:
--- freq=3125009 c1=232775435882 c2=232778559918 expected to sleep 1000 milliseconds, but slept for 999 ---
Win8.1 vbox vm:
--- freq=2186688 c1=144158294 c2=146345314 expected to sleep 1000 milliseconds, but slept for 1000 ---
I don't have winxp installation to test, but it looks like you was unlucky to hit this system problem msdn talks about, or something like that.(In reply to Alex Brainman from comment #10)
(In reply to Nikolay Sivov from comment #9)
Yes, for Wine QPC would be preferred currently, as long as we don't have an acceptable solution that updates this process memory data you're using (and having another entity like a separate thread to update it probably won't help performance, but it needs testing).
I understand. But I am not sure there is enough Go programs running on WINE for Go Team to invest their time maintaining WINE support.
Sure, I don't expect you to. Maybe someone interested enough will.