summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
2019-05-18Fix tests not running locallyGuillaume Gomez-1/+1
2019-05-17Update the compiler_builtins crateAlex Crichton-1/+1
This updates to 0.1.13 for `compiler_builtins`, published to fix a few issues. The feature changes here are updated because `compiler_builtins` no longer enables the `c` feature by default but we want to do so through our build still. Closes #60747 Closes #60782
2019-05-15Auto merge of #60832 - petrochenkov:CLazy, r=Mark-Simulacrumbors-0/+4
CMake: Do not print installation messages for up-to-date files Closes https://github.com/rust-lang/rust/issues/60830
2019-05-15Auto merge of #60775 - hellow554:no_bitrig, r=joshtriplettbors-1/+0
Remove bitrig support from rust Resolves #60743 using `find` and `rg` I delete every occurence of "bitrig" in the sources, expect for the llvm submodule (is this correct?). There's also this file https://github.com/rust-lang/rls/blob/5b8e99bb61958ca8abcb7c5eda70521726be1065/rls-analysis/test_data/rust-analysis/libstd-af9bacceee784405.json which contains a bitrig string in it. What to do with that?
2019-05-15rustbuild/LLVM: Do not print installation messages for up-to-date filesVadim Petrochenkov-0/+4
2019-05-14Rollup merge of #60719 - varkor:xpy-test-folder, r=Mark-SimulacrumMazdak Farrokhzad-2/+13
Allow subdirectories to be tested by x.py test Fixes https://github.com/rust-lang/rust/issues/60718. As far as I can tell, multiple `--test-args` flags are ignored (only the first is respected), so if you specify a subdirectory, you won't also be able to filter using `--test-args`. If you don't specify a subdirectory, `--test-args` will continue working as usual, so this is strictly an improvement on the current state of affairs.
2019-05-14Add commentvarkor-0/+6
2019-05-13Remove bitrig support from rustMarcel Hellwig-1/+0
2019-05-11Allow subdirectories to be tested by x.py testvarkor-2/+7
2019-05-10Make tests compatible with musl hostMateusz Mikuła-0/+4
2019-05-09remove unneeded `extern crate`s from build toolsAndy Russell-21/+31
2019-05-05Update getopts to 0.2.19varkor-1/+1
2019-05-03Rollup merge of #60401 - JohnTitor:rename-log, r=davidtwcoMazdak Farrokhzad-1/+1
Rename `RUST_LOG` to `RUSTC_LOG` cc: #57985 I think we should also change these submodules: - rustc-guide - Cargo (rename to `CARGO_LOG`, cc: https://github.com/rust-lang/cargo/pull/6605, https://github.com/rust-lang/cargo/issues/6189) - miri - rls - rustfmt r? @davidtwco
2019-05-02Update getopts to 0.2.18varkor-1/+1
This is a proof-of-concept that the dependency unification fix works.
2019-05-02Prevent dependencies between std/test/rustc unifying with each othervarkor-4/+20
2019-05-02Auto merge of #60379 - froydnj:bootstrap-progress-fixes, r=kennytmbors-3/+9
intelligently handle older version of git in bootstrap If we fail to run with `--progress`, try running without instead. Fixes #57080.
2019-05-02Auto merge of #60156 - RalfJung:macos-rand, r=oli-obk,alexcrichtonbors-0/+1
use SecRandomCopyBytes on macOS in Miri This is a hack to fix https://github.com/rust-lang/miri/issues/686: on macOS, rustc will open `/dev/urandom` to initialize a `HashMap`. That's quite hard to emulate properly in Miri without a full-blown implementation of file descriptors. However, Miri needs an implementation of `SecRandomCopyBytes` anyway to support [getrandom](https://crates.io/crates/getrandom), so using it here should work just as well. This will only have an effect when libstd is compiled specifically for Miri, but that will generally be the case when people use `cargo miri`. This is clearly a hack, so I am opening this to start a discussion about whether we are okay with such a hack or not. Cc @oli-obk
2019-04-30Auto merge of #60262 - michaelwoerister:pgo-preinlining-pass, r=alexcrichtonbors-51/+22
PGO: Add a run-make test that makes sure that PGO profiling data is used by the compiler during optimizations. From the tests comment section: ``` # This test makes sure that PGO profiling data leads to cold functions being # marked as `cold` and hot functions with `inlinehint`. # The test program contains an `if` were actual execution only ever takes the # `else` branch. Accordingly, we expect the function that is never called to # be marked as cold. ``` r? @alexcrichton
2019-04-30Rename to RUSTC_LOGYuki OKUSHI-1/+1
2019-04-30Add local LLD to the PATH for run-make-fulldeps tests.Michael Woerister-0/+15
2019-04-29intelligently handle older version of git in bootstrapNathan Froyd-3/+9
If we fail to run with `--progress`, try running without instead. Fixes #57080.
2019-04-29bootstrap: Don't add LLVM's bin directory to the PATH for tool invocations.Michael Woerister-51/+0
2019-04-29compiletest: Make LLVM's bin directory available to run-make-fulldeps tests.Michael Woerister-0/+7
2019-04-27Rollup merge of #60315 - pietroalbini:fix-tools-version, r=Mark-SimulacrumMazdak Farrokhzad-2/+2
bootstrap: use correct version numbers for llvm-tools and lldb The current URLs for the `llvm-tools` and `lldb` components are a bit broken right now: ``` https://static.rust-lang.org/dist/2019-04-25/llvm-tools-1.34.1 (fc50f328b 2019-04-24)-aarch64-unknown-linux-gnu.tar.gz ``` This PR uses proper version numbers for those. Tested a dist build locally and everything works. r? @Mark-Simulacrum
2019-04-26bootstrap: use correct version numbers for llvm-tools and lldbPietro Albini-2/+2
2019-04-26include rustc-std-workspace-alloc in rust-srcRalf Jung-0/+1
2019-04-25when testing Miri, compile libstd for MiriRalf Jung-0/+1
2019-04-25Rollup merge of #60038 - michaelwoerister:pgo-updates-2, r=alexcrichtonMazdak Farrokhzad-2/+2
Add codegen test for PGO instrumentation. This PR adds a codegen test that makes sure that LLVM actually generates instrumentation code when we enable PGO instrumentation in `rustc`. The second commit updates a test case to the new commandline option syntax introduced in #59874. Without the fix the test still works, but it confusingly creates a directory called `test.profraw`, which usually is the name of the _file_ where profiling data is collected.
2019-04-20Deny rust_2018_idioms globallyPhilipp Hansch-0/+1
2019-04-18Prefix PROFILER_SUPPORT and SANITIZER_SUPPORT test env vars with RUSTC_ to ↵Michael Woerister-2/+2
make things clearer.
2019-04-17Rollup merge of #60003 - petrhosek:llvm-lto-lld, r=cramertjMazdak Farrokhzad-2/+4
LLD is not supported on Darwin Don't enable LLD when LTO is enabled on Darwin.
2019-04-17Deny `internal` in stage0Mateusz Mikuła-3/+1
2019-04-17bump bootstrap; nightly => 1.36.Mazdak Farrokhzad-1/+1
2019-04-17bump bootstrap; remove redundant imports.Mazdak Farrokhzad-2/+0
2019-04-15LLD is not supported on DarwinPetr Hosek-2/+4
Don't enable LLD when LTO is enabled on Darwin.
2019-04-14Rollup merge of #59911 - ↵Mazdak Farrokhzad-31/+0
pnkfelix:revert-pr-59401-to-fix-emit-stack-sizes-gc-sections-ld-gold-bug, r=alexcrichton Revert "compile crates under test w/ -Zemit-stack-sizes" Revert PR #59401 to fix issue #59652 (a stable-to-beta regression). This is result of squashing two revert commits: Revert "compile all crates under test w/ -Zemit-stack-sizes" This reverts commit 7d365cf27f4249fc9b61ba8abfc813abe43f1cb7. Revert "bootstrap: build compiler-builtins with -Z emit-stack-sizes" This reverts commit 8b8488ce8fc047282e7159343f30609417f9fa39. ---- (My intention is that someone can re-add this code again later, either after the `ld.gold` issue itself is fixed, or with safe-guards to check whether `ld.gold` is in use and then issuing warnings about the problems here when they arise.)
2019-04-12Revert PR #59401 to fix issue #59652 (a stable-to-beta regression).Felix S. Klock II-31/+0
This is result of squashing two revert commits: Revert "compile all crates under test w/ -Zemit-stack-sizes" This reverts commit 7d365cf27f4249fc9b61ba8abfc813abe43f1cb7. Revert "bootstrap: build compiler-builtins with -Z emit-stack-sizes" This reverts commit 8b8488ce8fc047282e7159343f30609417f9fa39.
2019-04-12Rollup merge of #59876 - integer32llc:update-trpl-to-mdbook-0.2, r=steveklabnikMazdak Farrokhzad-4/+4
Update TRPL to use mdbook 0.2 I ran linkchecker locally and it passed. Let's see if I did it correctly...
2019-04-11Update TRPL to use mdbook 0.2Carol (Nichols || Goulding)-4/+4
2019-04-10Don't build test helpers for wasm32John Kåre Alsaker-1/+4
2019-04-10Don't require a C compiler on wasm32John Kåre Alsaker-0/+5
2019-04-10Update cmake, cc and compiler_builtins for VS 2019 supportJohn Kåre Alsaker-2/+2
2019-04-07Revert "Auto merge of #57842 - gnzlbg:extract_libtest, r=gnzlbg"Jacob Greenfield-0/+1
This reverts commit 3eb4890dfe6db0279fdd3cda19f9643873ae3db9, reversing changes made to 7a4df3b53da369110984a2b57419c05a53e33b38.
2019-04-04Auto merge of #59089 - petrhosek:llvm-unwind, r=petrhosekbors-0/+8
Support using LLVM's libunwind as the unwinder implementation This avoids the dependency on host libraries such as libgcc_s which may be undesirable in some deployment environments where these aren't available.
2019-04-04Auto merge of #59684 - Centril:rollup-n7pnare, r=Centrilbors-0/+5
Rollup of 6 pull requests Successful merges: - #59316 (Internal lints take 2) - #59663 (Be more direct about borrow contract) - #59664 (Updated the documentation of spin_loop and spin_loop_hint) - #59666 (Updated the environment description in rustc.) - #59669 (Reduce repetition in librustc(_lint) wrt. impl LintPass by using macros) - #59677 (rustfix coverage: Skip UI tests with non-json error-format) Failed merges: r? @ghost
2019-04-03Support using LLVM's libunwind as the unwinder implementationPetr Hosek-0/+8
This avoids the dependency on host libraries such as libgcc_s which may be undesirable in some deployment environments where these aren't available.
2019-04-03Add unstable-options flag to stage!=0flip1995-0/+5
2019-04-03Revert rust-lld place changes.O01eg-2/+1
2019-03-31Fix custom relative libdir.O01eg-11/+36
Uses relative libdir to place libraries on all stages. Adds verbose installation output.
2019-03-30Don't ignore git for LLVM infoJosh Stone-19/+22