diff options
| author | kennytm <kennytm@gmail.com> | 2018-04-14 18:50:41 +0800 |
|---|---|---|
| committer | kennytm <kennytm@gmail.com> | 2018-04-14 18:50:41 +0800 |
| commit | 0e9d6f9bb0ed675c82c30ca6a3227731f2facf6a (patch) | |
| tree | a00a2bd501dfb0d8bb08075a8a5e15fec408b9e7 /src/test/debuginfo/enum-thinlto.rs | |
| parent | 709ec4010d620f5942922b722ee2388df6f51b53 (diff) | |
| parent | 3366032ab70f72763bdf45c7f1257aa20b4229ca (diff) | |
| download | rust-0e9d6f9bb0ed675c82c30ca6a3227731f2facf6a.tar.gz rust-0e9d6f9bb0ed675c82c30ca6a3227731f2facf6a.zip | |
Rollup merge of #49864 - QuietMisdreavus:doctest-target-features, r=GuillaumeGomez
add target features when extracting and running doctests When rendering documentation, rustdoc will happily load target features into the cfg environment from the current target, but fails to do this when doing anything with doctests. This would lead to situations where, thanks to https://github.com/rust-lang/rust/pull/48759, functions tagged with `#[target_feature]` couldn't run doctests, thanks to the automatic `#[doc(cfg(target_feature = "..."))]`. Currently, there's no way to pass codegen options to rustdoc that will affect its rustc sessions, but for now this will let you use target features that come default on the platform you're targeting. Fixes https://github.com/rust-lang/rust/issues/49723
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions