Replace the legacy __sync built-in functions with __atomic ones
authorAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
Wed, 11 Jan 2023 08:19:44 +0000 (08:19 +0000)
committerJochen Sprickerhof <jspricke@debian.org>
Wed, 11 Jan 2023 08:19:44 +0000 (08:19 +0000)
commit4d3df2e59feda02277287c1cb5894c942852e89d
treeaef384ac6ffc3ab5a55a7989733c8cf538c8c1b3
parent667d227e7fbf76ab59aeb61e265e2d5873850016
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