This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/63829] _Lock_policy used in thread.cc can cause incompatibilities with binaries using different -mcpu
- From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Jan 2015 18:54:48 +0000
- Subject: [Bug libstdc++/63829] _Lock_policy used in thread.cc can cause incompatibilities with binaries using different -mcpu
- Auto-submitted: auto-generated
- References: <bug-63829-4 at http dot gcc dot gnu dot org/bugzilla/>
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 that code is forwards compatible to later architectures.
It's a really bad idea for the headers used in user code to be changing this
decision dynamically.