https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.42.0 2020-01-22T23:19:36+00:00 2020-01-22T23:19:36+00:00 Aaron Green nopsledder@users.noreply.github.com 2020-01-15T23:48:53+00:00 urn:sha1:4210409f443a40c72876e5e8398e8652a47a2ba6 This change adds the x86_64-fuchsia and aarch64-fuchsia LLVM targets to those allowed to invoke -Zsanitizer. Currently, the only overlap between compiler_rt sanitizers supported by both rustc and Fuchsia is ASan. 2020-01-11T03:02:24+00:00 Mazdak Farrokhzad twingoow@gmail.com 2020-01-11T03:02:24+00:00 urn:sha1:8c0c5c7e65479eaac21b26980efeff7a9b893e60 Add some missing timers Based on https://github.com/rust-lang/rust/pull/67988 r? @wesleywiser 2020-01-10T23:26:21+00:00 bors bors@rust-lang.org 2020-01-10T23:26:21+00:00 urn:sha1:e6217972644588a3be4fecb85b195f17b0220047 build-std compatible sanitizer support ### Motivation When using `-Z sanitizer=*` feature it is essential that both user code and standard library is instrumented. Otherwise the utility of sanitizer will be limited, or its use will be impractical like in the case of memory sanitizer. The recently introduced cargo feature build-std makes it possible to rebuild standard library with arbitrary rustc flags. Unfortunately, those changes alone do not make it easy to rebuild standard library with sanitizers, since runtimes are dependencies of std that have to be build in specific environment, generally not available outside rustbuild process. Additionally rebuilding them requires presence of llvm-config and compiler-rt sources. The goal of changes proposed here is to make it possible to avoid rebuilding sanitizer runtimes when rebuilding the std, thus making it possible to instrument standard library for use with sanitizer with simple, although verbose command: ``` env CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_RUSTFLAGS=-Zsanitizer=thread cargo test -Zbuild-std --target x86_64-unknown-linux-gnu ``` ### Implementation * Sanitizer runtimes are no long packed into crates. Instead, libraries build from compiler-rt are used as is, after renaming them into `librusc_rt.*`. * rustc obtains runtimes from target libdir for default sysroot, so that they are not required in custom build sysroots created with build-std. * The runtimes are only linked-in into executables to address issue #64629. (in previous design it was hard to avoid linking runtimes into static libraries produced by rustc as demonstrated by sanitizer-staticlib-link test, which still passes despite changes made in #64780). cc @kennytm, @japaric, @firstyear, @choller 2020-01-09T21:38:40+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2020-01-09T02:48:00+00:00 urn:sha1:b650e91cf40500b60475c17ff289e1db761d7836 2020-01-09T06:54:02+00:00 Tomasz Miąsko tomasz.miasko@gmail.com 2019-11-07T00:00:00+00:00 urn:sha1:0c6b1a7e3c54ff3a5ef6744073281b00368749c8 2020-01-09T06:06:40+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2020-01-07T20:34:08+00:00 urn:sha1:5427601e9ed173ad8e36adf02e5883729753af20 2020-01-05T11:49:22+00:00 Mazdak Farrokhzad twingoow@gmail.com 2020-01-05T01:37:57+00:00 urn:sha1:ebfd8673a791661d9cb526d9994f2f6bbfa49348 2020-01-05T01:57:14+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2020-01-01T01:24:05+00:00 urn:sha1:5a485ce4a3767bcac6bcc7bf66867c59c30eaeb1 2020-01-02T12:57:04+00:00 Mazdak Farrokhzad twingoow@gmail.com 2020-01-01T18:30:57+00:00 urn:sha1:4ff12ce4c14d348dfe53d1f74ab53c878f4fb4f8 2019-12-25T15:35:54+00:00 Lzu Tao taolzu@gmail.com 2019-12-25T15:35:54+00:00 urn:sha1:3a2ef17194d7bfe56e75a3504327b38bcad979ef see accouncement at https://docs.microsoft.com/welcome-to-docs