https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
--- Comment #8 from Richard Earnshaw ---
From a discussion on IRC:
What's the general story on lock policies?
Are environments supposed to support all three?
(if possible)
no. it's something only used in std::shared_ptr, and generally entirely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
Jonathan Wakely changed:
What|Removed |Added
CC||rearnsha at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
--- Comment #6 from Richard Earnshaw rearnsha at gcc dot gnu.org ---
arm linux code should always be using the _S_atomic sequences. When the
processor doesn't have the required instructions, kernel helper routines will
be used. This ensures
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
--- Comment #5 from Jonathan Wakely redi at gcc dot gnu.org ---
(In reply to Aaron Graham from comment #3)
I've solved this problem in my own setup by building the toolchain and
application binaries with the same -mcpu.
A more general
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63829
Aaron Graham aaron at aarongraham dot com changed:
What|Removed |Added
Component|c++ |libstdc++
