diff options
| author | bors <bors@rust-lang.org> | 2020-09-10 10:06:44 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-09-10 10:06:44 +0000 |
| commit | 25b2f4861222d6507598149f576e7d25dc308c8c (patch) | |
| tree | fe5f65adf1860096d3dfbaa6e86192a4e7129662 /library/std/src/os/linux/mod.rs | |
| parent | a18b34d9793a88142c122f83fe53683f58f26ecc (diff) | |
| parent | 75a2c68fb66fb9aac2805e298d20578019a0c129 (diff) | |
| download | rust-25b2f4861222d6507598149f576e7d25dc308c8c.tar.gz rust-25b2f4861222d6507598149f576e7d25dc308c8c.zip | |
Auto merge of #76378 - petrochenkov:lldtest, r=Mark-Simulacrum
rustbuild: Build tests with LLD if `use-lld = true` was passed Addresses https://github.com/rust-lang/rust/pull/76127#discussion_r479932392. Our test suite is generally ready to run with an explicitly specified linker (https://github.com/rust-lang/rust/pull/45191), so LLD specified with `use-lld = true` works as well. Only 4 tests fail (on `x86_64-pc-windows-msvc`): ``` ui/panic-runtime/lto-unwind.rs run-make-fulldeps/debug-assertions run-make-fulldeps/foreign-exceptions run-make-fulldeps/test-harness ``` All of them are legitimate issues with LLD (or at least with combination Rust+LLD) and manifest in segfaults on access to TLS (https://github.com/rust-lang/rust/pull/76127#issuecomment-683473325). UPD: These issues are caused by https://github.com/rust-lang/rust/issues/72145 and appear because I had `-Ctarget-cpu=native` set. UPD: Further commits build tests with LLD for non-MSVC targets and propagate LLD to more places when `use-lld` is enabled.
Diffstat (limited to 'library/std/src/os/linux/mod.rs')
0 files changed, 0 insertions, 0 deletions