Replace the legacy __sync built-in functions with __atomic ones
authorAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
Thu, 24 Feb 2022 16:58:51 +0000 (16:58 +0000)
committerRoger Shimizu <rosh@debian.org>
Thu, 24 Feb 2022 16:58:51 +0000 (16:58 +0000)
commit070730093dca667f301541d4eb3bcd6cfd6e6a8a
tree9de9de1f99c8ca263484985cadb6901d12d71871
parent0aa803fec69c2045d7d6f8f9d812d012e06dc2ce
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