Replace the legacy __sync built-in functions with __atomic ones
authorAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
Tue, 22 Mar 2022 22:50:07 +0000 (22:50 +0000)
committerPeter Michael Green <plugwash@raspbian.org>
Tue, 22 Mar 2022 22:50:07 +0000 (22:50 +0000)
commit572860474438b935385b27f3144f875a3e83a40f
treebb33abf9849bdb72b224891c2216b59309c6dd49
parentf4e59920057c3a62f85d6d46b874046f77772bf1
Replace the legacy __sync built-in functions with __atomic ones

Last-Update: 2016-10-04
Forwarded: not-needed

libunwind uses the built-in __sync_* functions which are deprecated by GCC and
should be replaced by __atomic_* ones. See the official manuals [1].

The legacy __sync functions do not require to specify the memory order but
__atomic ones do, so we choose the strongest one: __ATOMIC_SEQ_CST.

We do this because __sync_fetch_and_add() is not supported on armel.

[1]: https://gcc.gnu.org/onlinedocs/gcc/_005f_005fsync-Builtins.html

Gbp-Pq: Topic external/libunwind
Gbp-Pq: Name legacy_built-in_sync_functions.patch
external/libunwind/include/libunwind_i.h