diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-01-14 11:31:52 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-14 11:31:52 +0100 |
| commit | 74cc0be8f6388aa2fc1ecaf18904c395a2306c40 (patch) | |
| tree | d138d06c2ae67548d568775becc767e99eec48b5 /src/rustllvm/RustWrapper.cpp | |
| parent | 36d68f5fb30a1bd7d3604401c03e4cf81c029a06 (diff) | |
| parent | 972bba7071d0e6b04194fa3c1108b991262dd502 (diff) | |
| download | rust-74cc0be8f6388aa2fc1ecaf18904c395a2306c40.tar.gz rust-74cc0be8f6388aa2fc1ecaf18904c395a2306c40.zip | |
Rollup merge of #57465 - jethrogb:jb/stablize-cfg-target-vendor, r=joshtriplett,Centril
Stabilize cfg_target_vendor This stabilizes the use of `cfg(target_vendor = "...")` and removes the corresponding `cfg_target_vendor` feature. Other unstable cfgs remain behind their existing feature gates. This functionality was added back in 2015 in #28612 to complete the coverage of target tuples (`<arch><sub>-<vendor>-<os>-<env>`). [RFC 131](https://github.com/rust-lang/rfcs/blob/master/text/0131-target-specification.md) governs the target specification, not including `target_vendor` seems to have just been an oversight. `target_os`, `target_family`, and `target_arch` are stable as of 1.0.0. `target_env` was also not mentioned in RFC 131, was added in #24777, never behind a feature_gate, and insta-stable at 1.1.0. The functionality is tested in [test/run-pass/cfg/cfg-target-vendor.rs](https://github.com/rust-lang/rust/blob/master/src/test/run-pass/cfg/cfg-target-vendor.rs). Closes #29718
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions