-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gcc: backport some upstream fixes #8052
Conversation
In order for GCC to use its implementation of __cxa_thread_atexit instead of mingw-w64's it is necessary to |
Should I add it? Are there any other packages affected by this change? |
Any C++ that uses thread_local objects would be affected. The current state of affairs with mingw-w64's implementation, paired with a dynamically linked libwinpthread (as is default with the toolchain distributed here) results in a use-after-free during destruction of such objects defined in the EXE. GCC's implementation, while having its own issues, at least is capable of avoiding that situation, so seemed to be the least-bad option. |
See also #7096 |
D'oh, doesn't seem to have helped the use-after-free situation, as I expected it to. In fact, it seems to have moved to the .dll instead...
|
Compared with current version of gcc in repo:
|
Sorry, I guess this patch/change turns out to be a wild goose chase, thought I had confirmed that this worked back in like October 😕 |
Fixes #8046