| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | atomics: some corrections to __sync builtins usage | wm4 | 2014-05-28 | 1 | -3/+3 |
| | | | | | | | | | | | | | We don't need to combine __sync_add_and_fetch with a memory barrier, since these intrinsics are documented as using a full barrier already. Use __sync_fetch_and_add instead of __sync_add_and_fetch; this gives atomic_fetch_add() the correct return value (although we don't use it). Use __sync_fetch_and_add to emulate atomic_load(). This should enforce the full barrier semantics better. (This trick is stolen from the FreeBSD based stdatomic.h emulation.) | ||||
| * | atomics: more correct usage of gcc/clang __atomic builtins | wm4 | 2014-05-21 | 1 | -11/+15 |
| | | | | | | | | | | | | This should be more correct. The builtins were made to directly map to C11, and the way we use them is now relatively close to how gcc implements atomics in 4.9. In particular, we make use of the load and store builtins. I'm not entirely sure why gcc didn't support stdatomic.h in 4.8 already. Maybe support for the builtins was incomplete or broken - so there's a lot of room for doubt about the correctness of this. | ||||
| * | atomics: switch to C11 stdatomic.h | wm4 | 2014-05-21 | 1 | -6/+36 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | build: make configure fail if both __atomic and __sync are not available | Stefano Pigozzi | 2014-01-01 | 1 | -1/+3 |
| | | |||||
| * | compat: use __atomic operations instead of __sync, when present | Alessandro Ghedini | 2013-12-31 | 1 | -2/+9 |
| | | | | | | Fixes #434 Fixes #437 | ||||
| * | Split mpvcore/ into common/, misc/, bstr/ | wm4 | 2013-12-17 | 1 | -0/+23 |
 |
index : mpv | |
| a free, open source, and cross-platform media player |
| summaryrefslogtreecommitdiffstats |