diff options
| author | Richard Earnshaw <rearnsha@arm.com> | 2025-01-27 13:52:05 +0000 |
|---|---|---|
| committer | Richard Earnshaw <rearnsha@arm.com> | 2025-01-28 13:54:02 +0000 |
| commit | a235c45354de9a89ba2f6f12d3aac42efc18f311 (patch) | |
| tree | 3dc15af6dd218fb283c3970d2f22c7b55eb16708 /gcc | |
| parent | 01339d29b7663d85eea6145eac2b1ad1da428c11 (diff) | |
| download | gcc-a235c45354de9a89ba2f6f12d3aac42efc18f311.zip gcc-a235c45354de9a89ba2f6f12d3aac42efc18f311.tar.gz gcc-a235c45354de9a89ba2f6f12d3aac42efc18f311.tar.bz2 | |
arm: libbacktrace: Check if the compiler supports __sync atomics
Older versions of the Arm architecture lack support for __sync
operations directly in hardware and require calls into appropriate
operating-system hooks. But such hooks obviously don't exist in a
freestanding environment.
Consquently, it is incorrect to assume during configure that such
functions will exist and we need a configure-time check to determine
whether or not these routines will work.
libbacktrace:
* configure.ac: Always check if the compiler supports __sync
operations.
* configure: Regenerated.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions