diff options
author | NRK <nrk@disroot.org> | 2023-10-18 20:32:16 +0600 |
---|---|---|
committer | sfan5 <sfan5@live.de> | 2023-10-20 21:31:09 +0200 |
commit | 2fa695c3f9d4164344228ef4083e87369de3bb33 (patch) | |
tree | 86479e5d70197a27615a55ee47cdb3d3502d63e7 /DOCS/tech-overview.txt | |
parent | 3fb4eb2ba47fea78e69937971974f42cba82d1df (diff) | |
download | mpv-2fa695c3f9d4164344228ef4083e87369de3bb33.tar.bz2 mpv-2fa695c3f9d4164344228ef4083e87369de3bb33.tar.xz |
osdep: drop atomic fallback
even msvc (which mpv apparently doesn't support) supports C11 atomics
now. no need to carry around fallback with subtle semantic differences.
Diffstat (limited to 'DOCS/tech-overview.txt')
-rw-r--r-- | DOCS/tech-overview.txt | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/DOCS/tech-overview.txt b/DOCS/tech-overview.txt index dd21322bbb..fefca1431d 100644 --- a/DOCS/tech-overview.txt +++ b/DOCS/tech-overview.txt @@ -434,8 +434,7 @@ See generally available literature. In mpv, we use pthread for this. Always keep locking clean. Don't skip locking just because it will work "in practice". (See undefined behavior section.) If your use case is simple, you may -use C11 atomics (osdep/atomic.h for partial C99 support), but most likely you -will only hurt yourself and others. +use C11 atomics, but most likely you will only hurt yourself and others. Always make clear which fields in a struct are protected by which lock. If a field is immutable, or simply not thread-safe (e.g. state for a single worker |