diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-06-09 12:04:04 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-09 12:04:04 +0900 |
| commit | da1a4498ca8d431c494ddf16689428b09e56784a (patch) | |
| tree | ab4f551c76fcbbc5110dfdb6350087cfd3f74c0b /compiler/rustc_mir/src/transform/coverage/debug.rs | |
| parent | 606feba5bbfa61ef9562fd2f583833ed5c13ffdc (diff) | |
| parent | aba85ff82077f80b6406cbaaf6a54afe6df98332 (diff) | |
| download | rust-da1a4498ca8d431c494ddf16689428b09e56784a.tar.gz rust-da1a4498ca8d431c494ddf16689428b09e56784a.zip | |
Rollup merge of #85982 - alexcrichton:doc-safe-wasm, r=jyn514
Enable rustdoc to document safe wasm intrinsics This commit fixes an issue not found during #84988 where rustdoc is used to document cross-platform intrinsics but it was requiring that functions which use `#[target_feature]` are `unsafe` erroneously, even if they're WebAssembly specific. Rustdoc today, for example, already has a special case where it enables annotations like `#[target_feature(enable = "simd128")]` on platforms other than WebAssembly. The purpose of this commit is to relax the "require all `#[target_feature]` functions are `unsafe`" requirement for all targets whenever rustdoc is running, enabling all targets to fully document other targets, such as WebAssembly, where intrinsics functions aren't always `unsafe`.
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions
