projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 64e09f4) | patch
Drop use of `volatile`
authorJonathan Lebon <jonathan@jlebon.com>
Mon, 2 Nov 2020 19:53:26 +0000 (14:53 -0500)
committerJonathan Lebon <jonathan@jlebon.com>
Mon, 2 Nov 2020 19:53:26 +0000 (14:53 -0500)
commitf895cf4fd264b2cf96c70c9f3991b47cf116d22f
tree21012befebbddcd92c4002b45ad0e972649dc4a9tree | snapshot
parent64e09f46b84f7dbbd960c05332583fb60f73233bcommit | diff
Drop use of `volatile`

As detailed in
gitlab.gnome.org/GNOME/glib/-/issues/600#note_877282, volatile
isn't actually needed in these contexts because the atomic operations
already give us strong enough guarantees. In GCC 11, this triggers a
diagnostic due to the volatile qualifier getting dropped anyway.

There is a WIP to do the same in glib:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719

This obsoletes this downstream patch:
https://src.fedoraproject.org/rpms/ostree/c/b8c5a6fb
src/libostree/ostree-diff.h diff | blob | history
src/libostree/ostree-enumtypes.c.template diff | blob | history
src/libostree/ostree-fetcher-soup.c diff | blob | history
src/libostree/ostree-remote-private.h diff | blob | history
src/libostree/ostree-repo-private.h diff | blob | history
src/libostree/ostree-sysroot-upgrader.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.