diff options
author | wm4 <wm4@nowhere> | 2014-05-21 01:04:47 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-05-21 02:21:18 +0200 |
commit | 8e7cf4bc992f13dbb523bb42d6b9de4bc2f486c2 (patch) | |
tree | 77f21515a336c368d2bb97eab11d950bed9f5c4d /player/client.h | |
parent | 2f65f0e2548f95b3b8ba6620efe6c0e3cb02420b (diff) | |
download | mpv-8e7cf4bc992f13dbb523bb42d6b9de4bc2f486c2.tar.bz2 mpv-8e7cf4bc992f13dbb523bb42d6b9de4bc2f486c2.tar.xz |
atomics: switch to C11 stdatomic.h
In my opinion, we shouldn't use atomics at all, but ok.
This switches the mpv code to use C11 stdatomic.h, and for compilers
that don't support stdatomic.h yet, we emulate the subset used by mpv
using the builtins commonly provided by gcc and clang.
This supersedes an earlier similar attempt by Kovensky. That attempt
unfortunately relied on a big copypasted freebsd header (which also
depended on much more highly compiler-specific functionality, defined
reserved symbols, etc.), so it had to be NIH'ed.
Some issues:
- C11 says default initialization of atomics "produces a valid state",
but it's not sure whether the stored value is really 0. But we rely on
this.
- I'm pretty sure our use of the __atomic... builtins is/was incorrect.
We don't use atomic load/store intrinsics, and access stuff directly.
- Our wrapper actually does stricter typechecking than the stdatomic.h
implementation by gcc 4.9. We make the atomic types incompatible with
normal types by wrapping them into structs. (The FreeBSD wrapper does
the same.)
- I couldn't test on MinGW.
Diffstat (limited to 'player/client.h')
0 files changed, 0 insertions, 0 deletions