diff options
author | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-05-13 12:10:13 +0100 |
---|---|---|
committer | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-07-02 09:27:05 +0100 |
commit | a8014c48c1a2a0398e49b04a08962355c7dcbb11 (patch) | |
tree | c5192d2a5a78a1da30995c578e98452b70ed35c0 /elf/nextmod2.c | |
parent | a87bc4ad93ba09f35adb9284fc932627e3b6990d (diff) | |
download | glibc-a8014c48c1a2a0398e49b04a08962355c7dcbb11.zip glibc-a8014c48c1a2a0398e49b04a08962355c7dcbb11.tar.gz glibc-a8014c48c1a2a0398e49b04a08962355c7dcbb11.tar.bz2 |
aarch64: fix pac-ret support in _mcount
Currently gcc -pg -mbranch-protection=pac-ret passes signed return
address to _mcount, so _mcount now has to always strip pac from the
frompc since that's from user code that may be built with pac-ret.
This is gcc PR target/94791: signed pointers should not escape and get
passed across extern call boundaries, since that's an ABI break, but
because existing gcc has this issue we work it around in glibc until
that is resolved. This is compatible with a fixed gcc and it is a nop
on systems without PAuth support. The bug was introduced in gcc-7 with
-msign-return-address=non-leaf|all support which in gcc-9 got renamed
to -mbranch-protection=pac-ret|pac-ret+leaf|standard.
strip_pac uses inline asm instead of __builtin_aarch64_xpaclri since
that is not a documented api and not available in all supported gccs.
Diffstat (limited to 'elf/nextmod2.c')
0 files changed, 0 insertions, 0 deletions