https://bugs.winehq.org/show_bug.cgi?id=55007
Chiitoo chiitoo@gentoo.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Version|unspecified |8.10 Resolution|--- |INVALID
--- Comment #3 from Chiitoo chiitoo@gentoo.org --- I forgot we normally strip CFLAGS for our Wine builds on Gentoo, so my actual usual CFLAGS are changed to:
-march=znver4 -O2 -pipe -mindirect-branch=thunk
In any case, this definitely doesn't seem to be as simple as it first seemed.
That is, it's not just related to -O2 or so from the looks of it, as I'm getting the crashes with -O1 as well now, and -znver* seems more likely to have more effect towards the crashes (GCC probably chose znver4 automagically even when I did not set it, though not sure what it set for mingw-toolchain GCC <12.3.0 or so which I think is around when it first got 'znver4').
Gone through around 300 builds with different settings, including '-march=x86-64', which with I don't remember getting the crash yet even when manually adding the other instructions znver activates per GCC documention, and I also didn't see the crashes with -march=bdver4 (although as discussed, that might not even be that interesting to chase, and may be inconsistent).
Then again, I forget if I replicated the issue with a plain build from git VS our package manager, even though I'm using the same flags there.
I suppose in the end this is a GCC bug, so perhaps this should be closed here, and I'll look into reporting this to the appropriate people.
I'll include the backtrace snippets with symbols, which I didn't quite have enough time to get for the initial report, in case someone bumps into the exact same issue.
Thank you!