aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2024-09-05 12:20:57 +0200
committerJakub Jelinek <jakub@gcc.gnu.org>2024-09-05 12:22:19 +0200
commit2379cbb94b2668227c237c94c82e3c49fe39fd0f (patch)
treeeaf29fe67f4d5158dfab3d7af76b39ad7c7e5c0e /gcc/cp
parenta50f54c0d06139d791b875e09471f2fc03af5b04 (diff)
downloadgcc-2379cbb94b2668227c237c94c82e3c49fe39fd0f.zip
gcc-2379cbb94b2668227c237c94c82e3c49fe39fd0f.tar.gz
gcc-2379cbb94b2668227c237c94c82e3c49fe39fd0f.tar.bz2
libsanitizer: On aarch64 use hint #34 in prologue of libsanitizer functions
When gcc is built with -mbranch-protection=standard, running sanitized programs doesn't work properly on bti enabled kernels. This has been fixed upstream with https://github.com/llvm/llvm-project/pull/84061 The following patch cherry picks that from upstream. For trunk we should eventually do a full merge from upstream, but I'm hoping they will first fix up the _BitInt libubsan support mess. 2024-09-05 Jakub Jelinek <jakub@redhat.com> * sanitizer_common/sanitizer_asm.h: Cherry-pick llvm-project revision 1c792d24e0a228ad49cc004a1c26bbd7cd87f030. * interception/interception.h: Likewise.
Diffstat (limited to 'gcc/cp')
0 files changed, 0 insertions, 0 deletions