diff options
| author | bors <bors@rust-lang.org> | 2021-04-02 23:33:01 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-04-02 23:33:01 +0000 |
| commit | 9b6c9b638e0148409b6568b61f763e87dc8fd3bf (patch) | |
| tree | 1ea35a5d526323112746615fd26f2ee4e4339d49 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 138fd56cf9598b4bf016634c768dca128a83a5d7 (diff) | |
| parent | 41875c82c7858735b1d028b04156c328715ca454 (diff) | |
| download | rust-9b6c9b638e0148409b6568b61f763e87dc8fd3bf.tar.gz rust-9b6c9b638e0148409b6568b61f763e87dc8fd3bf.zip | |
Auto merge of #81866 - nagisa:nagisa/sanitizer-support-target-prop, r=tmiasko
Maintain supported sanitizers as a target property
In an effort to remove a hard-coded allow-list for target-sanitizer support correspondence, this PR moves the configuration to the target options.
Perhaps the one notable change made in this PR is this doc-comment:
```rust
/// The sanitizers supported by this target
///
/// Note that the support here is at a codegen level. If the machine code with sanitizer
/// enabled can generated on this target, but the necessary supporting libraries are not
/// distributed with the target, the sanitizer should still appear in this list for the target.
```
Previously the target would typically be added to the allow-list at the same time as the supporting runtime libraries are shipped for the target. However whether we ship the runtime libraries or not needn't be baked into the compiler; and if we don't users will receive a significantly more directed error about library not being found.
Fixes #81802
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions