https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.34.2 2019-01-03T21:52:36+00:00 2019-01-03T21:52:36+00:00 Alex Crichton alex@alexcrichton.com 2019-01-02T21:23:45+00:00 urn:sha1:ccbf28eae8b345db3ede51112cc32c756a084bd9 In #56986 the linkage of jemalloc to the compiler was switched from the driver library to the rustc binary to ensure that only rustc itself uses jemalloc. In doing so, however, it turns out jemalloc wasn't actually linked in at all! None of the symbols were referenced so the static library wasn't used. This means that jemalloc wasn't pulled in at all. This commit performs a bit of a dance to reference jemalloc symbols, attempting to pull it in despite LLVM's optimizations. Closes #57115 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c 2018-12-19T16:27:23+00:00 Alex Crichton alex@alexcrichton.com 2018-12-19T16:27:23+00:00 urn:sha1:ba0ed5b13f23dd6e4ff0047a653ee615b84a67f2 This commit moves jemalloc to just the rustc binary rather than the rustc_driver shared library, enusring that it's only used for binaries that opt-in to it like rustc rather than other binaries using librustc_driver like rustdoc/rls/etc. This will hopefully address #56980 2018-04-16T17:50:58+00:00 kennytm kennytm@gmail.com 2018-04-16T17:50:58+00:00 urn:sha1:ccd2c403ac6d1b92c49985d09c4b1d0af8f651e1 Prevent broken pipes causing ICEs As the private `std::io::print_to` panics if there is an I/O error, which is used by `println!`, the compiler would ICE if one attempted to use a broken pipe (e.g. `rustc --help | false`). This introduces a new (private) macro `try_println!` which allows us to avoid this. As a side note, it seems this macro might be useful publicly (and actually there seems to be [a crate specifically for this purpose](https://crates.io/crates/try_print/)), though that can probably be left for a future discussion. One slight alternative approach would be to simply early exit without an error (i.e. exit code `0`), which [this comment](https://github.com/rust-lang/rust/issues/34376#issuecomment-377822526) suggests is the usual approach. I've opted not to take that approach initially, because I think it's more helpful to know when there is a broken pipe. Fixes #34376. 2018-04-11T10:05:13+00:00 varkor github@varkor.com 2018-04-10T22:55:41+00:00 urn:sha1:7ab31f6556c2cce433695b113f53d6275edd724d 2018-04-11T02:04:57+00:00 Mark Simulacrum mark.simulacrum@gmail.com 2018-04-09T17:21:43+00:00 urn:sha1:53718d2ef1729c987531dc94971c905815daef55 2018-03-28T09:51:25+00:00 Tatsuyuki Ishi ishitatsuyuki@gmail.com 2018-03-28T09:51:25+00:00 urn:sha1:50ca86be2438369dd1263c619a3bac21bd30a37f 2018-03-18T14:05:28+00:00 Tatsuyuki Ishi ishitatsuyuki@gmail.com 2018-03-06T04:33:36+00:00 urn:sha1:1bb89f1b3cf1e4b5fa83391872136251c0030c1e 2016-02-11T18:42:28+00:00 Alex Crichton alex@alexcrichton.com 2015-11-19T23:20:12+00:00 urn:sha1:046e6874c47ec55e23b7a566bca51d2920562485 This commit is the start of a series of commits which start to replace the makefiles with a Cargo-based build system. The aim is not to remove the makefiles entirely just yet but rather just replace the portions that invoke the compiler to do the bootstrap. This commit specifically adds enough support to perform the bootstrap (and all the cross compilation within) along with generating documentation. More commits will follow up in this series to actually wire up the makefiles to call this build system, so stay tuned!