diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-08-15 19:32:35 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-15 19:32:35 +0200 |
| commit | 3075644a3db0e529e5e9e74cf5ea74a0a638d1fe (patch) | |
| tree | ae613eb4851f8a4ca6b7a3f6d64dffb5a4f45508 /compiler/rustc_parse/src | |
| parent | d2b5aa6552c8acf67f38a2ad92062a32ec542f08 (diff) | |
| parent | b368dcb246c5aedb087034e0f62941d038799f38 (diff) | |
| download | rust-3075644a3db0e529e5e9e74cf5ea74a0a638d1fe.tar.gz rust-3075644a3db0e529e5e9e74cf5ea74a0a638d1fe.zip | |
Rollup merge of #128348 - dingxiangfei2009:allow-shadow-call-stack-sanitizer, r=tmandry
Unconditionally allow shadow call-stack sanitizer for AArch64 It is possible to do so whenever `-Z fixed-x18` is applied. cc ``@Darksonn`` for context The reasoning is that, as soon as reservation on `x18` is forced through the flag `fixed-x18`, on AArch64 the option to instrument with [Shadow Call Stack sanitizer](https://clang.llvm.org/docs/ShadowCallStack.html) is then applicable regardless of the target configuration. At the every least, we would like to relax the restriction on specifically `aarch64-unknonw-none`. For this option, we can include a documentation change saying that users of compiled objects need to ensure that they are linked to runtime with Shadow Call Stack instrumentation support. Related: #121972
Diffstat (limited to 'compiler/rustc_parse/src')
0 files changed, 0 insertions, 0 deletions