https://bugs.winehq.org/show_bug.cgi?id=36758
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #5 from Sebastian Lackner sebastian@fds-team.de --- I am not sure if this is really a gcc bug. I am using Archlinux, which also ships a very new gcc version
--- snip --- $ gcc --version gcc (GCC) 4.9.1 20140903 (prerelease) --- snip ---
Nevertheless, this problem doesn't occur always - it only occurs with a small probability. I am able to reproduce this even with -O0, so its most likely not an optimization issue.
Could someone with an old version of gcc please test that this issue really doesn't exist yet? I suspect that it might be timing related or some kind of multithreaded issue.