Replace the legacy __sync built-in functions with __atomic ones
authorAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
Mon, 27 Jun 2022 17:30:12 +0000 (18:30 +0100)
committerRoger Shimizu <rosh@debian.org>
Mon, 27 Jun 2022 17:30:12 +0000 (18:30 +0100)
commit81d513407bd99f5d10cf3d9333dfd4bac6054e0f
tree4141b3de33b4e628dfbb42a956c02e73a6cdb389
parent98e0799fa6e9598097f8d16d01291921419b42d9
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