https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106170
--- Comment #7 from cqwrteur <unlvsur at live dot com> --- (In reply to Richard Biener from comment #6) > Another possibility would be to white-list targets that should have a > thread-safe plugin. std::atomic is freestanding. so technically adding a spin lock for an unsupported target would be possible. However, it is still risky. Whatever, for windows, I would suggest for using win32 CriticalSection api.
