diff options
| author | Wilco Dijkstra <wdijkstr@arm.com> | 2022-09-22 15:32:40 +0100 |
|---|---|---|
| committer | Wilco Dijkstra <wdijkstr@arm.com> | 2022-09-23 15:59:56 +0100 |
| commit | d1babeb32de5dae8893c640bd925357b218d846c (patch) | |
| tree | c5ee8e42e03e6a4caf2eb645d5f9b7a8bdbdb6e1 /nptl/sem_post.c | |
| parent | 8114b95cef10a5a1fc3e529ab8b3a75f56fe889a (diff) | |
| download | glibc-d1babeb32de5dae8893c640bd925357b218d846c.tar.gz glibc-d1babeb32de5dae8893c640bd925357b218d846c.tar.xz glibc-d1babeb32de5dae8893c640bd925357b218d846c.zip | |
Use C11 atomics instead of atomic_increment(_val)
Replace atomic_increment and atomic_increment_val with atomic_fetch_add_relaxed. One case in sem_post.c uses release semantics (see comment above it). The others are simple counters and do not protect any shared data from concurrent accesses. Passes regress on AArch64. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'nptl/sem_post.c')
| -rw-r--r-- | nptl/sem_post.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nptl/sem_post.c b/nptl/sem_post.c index 9e5741753a..7ec21e92eb 100644 --- a/nptl/sem_post.c +++ b/nptl/sem_post.c @@ -91,7 +91,7 @@ __old_sem_post (sem_t *sem) /* We must need to synchronize with consumers of this token, so the atomic increment must have release MO semantics. */ atomic_write_barrier (); - (void) atomic_increment_val (futex); + atomic_fetch_add_release (futex, 1); /* We always have to assume it is a shared semaphore. */ futex_wake (futex, 1, LLL_SHARED); return 0; |