aboutsummaryrefslogtreecommitdiff
path: root/posix/uname-values.h
diff options
context:
space:
mode:
authorSzabolcs Nagy <szabolcs.nagy@arm.com>2020-06-30 11:12:40 +0100
committerSzabolcs Nagy <szabolcs.nagy@arm.com>2020-07-02 09:27:05 +0100
commit52733817c888141129929df79dad7704ed44e335 (patch)
treed66e147be2a3d74861450e72e94ddea384835288 /posix/uname-values.h
parent582f1a25ace0bffb2e8fbec9a85d3fcaf55b84e5 (diff)
downloadglibc-52733817c888141129929df79dad7704ed44e335.zip
glibc-52733817c888141129929df79dad7704ed44e335.tar.gz
glibc-52733817c888141129929df79dad7704ed44e335.tar.bz2
aarch64: ensure objects are BTI compatible
When glibc is built with branch protection (i.e. with a gcc configured with --enable-standard-branch-protection), all glibc binaries should be BTI compatible and marked as such. It is easy to link BTI incompatible objects by accident and this is silent currently which is usually not the expectation, so this is changed into a link error. (There is no linker flag for failing on BTI incompatible inputs so all warnings are turned into fatal errors outside the test system when building glibc with branch protection.) Unfortunately, outlined atomic functions are not BTI compatible in libgcc (PR libgcc/96001), so to build glibc with current gcc use 'CC=gcc -mno-outline-atomics', this should be fixed in libgcc soon and then glibc can be built and tested without such workarounds.
Diffstat (limited to 'posix/uname-values.h')
0 files changed, 0 insertions, 0 deletions