summary refs log tree commit diff
path: root/src/Cargo.lock
AgeCommit message (Collapse)AuthorLines
2017-07-13[beta] Remove rls from the workspace and extended buildsJosh Stone-247/+0
Its git dependencies don't work when building with vendored crates, so for now it will just be removed from the workspace and disabled in the rustbuild rules. cc #42719
2017-07-13Update the `cargo` submoduleAlex Crichton-5/+3
Notably pull in an update to the `jobserver` crate to have Cargo set the `CARGO_MAKEFLAGS` environment variable instead of the `MAKEFLAGS` environment variable.
2017-06-12update git2Marc-Antoine Perennou-10/+16
Fixes build with libressl Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2017-06-08[beta] Update rls/cargo submodulesAlex Crichton-76/+46
This updates the cargo submodule to the latest tip of Cargo, along with an accompanying update to the `rls` submodule to keep it compiling.
2017-06-02Rollup merge of #42343 - cuviper:install-executables, r=alexcrichtonMark Simulacrum-5/+5
Update rust-installer for Windows executable mode It now marks a few whitelisted extensions as executable in the tarball, so Windows packages can be extracted on other platforms and directly execute install.sh. It also includes a fix for the chmod on bulk dirs, so now the html docs won't be marked executable en masse. Fixes #42121 r? @alexcrichton
2017-06-01Support VS 2017Brian Anderson-17/+18
Fixes #38584
2017-05-31Update rust-installer for Windows executable modeJosh Stone-5/+5
It now marks a few whitelisted extensions as executable in the tarball, so Windows packages can be extracted on other platforms and directly execute install.sh. It also includes a fix for the chmod on bulk dirs, so now the html docs won't be marked executable en masse. Fixes #42121 r? @alexcrichton
2017-05-28Updated locked version of libgit2Alex Crichton-7/+8
This should include a fix for rust-lang/cargo#4091 with an updated version of libgit2. Closes rust-lang/cargo#4091
2017-05-24Update Cargo submoduleAlex Crichton-29/+0
Contains a fix for rust-lang/cargo#4081
2017-05-18Unify all stage2 tools into a workspaceTatsuyuki Ishi-71/+1048
This avoids double compiled Cargo. Hopefully this would speed up (extended) compilation for ~10m. Notes: when updating Cargo submodule, the replacement version may also need to be updated.
2017-05-16Auto merge of #41853 - Keruspe:install, r=alexcrichtonbors-3/+3
rustbuild: add support for --bindir and --sysconfdir This depends on https://github.com/rust-lang/rust-installer/pull/59 and we'll need to udpate the rust-installer submodule once it gets merged for it to work Fixes #41644
2017-05-16update lzma-sys to 0.1.4Marc-Antoine Perennou-3/+3
fixes build when DESTDIR is set Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2017-05-16Auto merge of #41565 - rkruppe:llvm-sys, r=eddybbors-3/+18
Make only rustc_trans depend on rustc_llvm With these changes, only rustc_trans depends directly on rustc_llvm (and no crate gained a new dependency on trans). This means changing LLVM doesn't rebuild librustc or rustc_metadata, only rustc_trans, rustc_driver and the rustc executable Also, rustc_driver technically doesn't know about LLVM any more (of course, it still handles a ton of options that conceptually refer to LLVM, but it delegates their implementation to trans). What I *didn't* implement was merging most or all of rustc_llvm into rustc_trans. I ran into a nasty bug, which was probably just a silly typo somewhere but I probably won't have the time to figure it out in the next week or two. I opened #41699 for that step. Fixes #41473
2017-05-15Remove (direct) rustc_llvm dependency from rustc_driverRobin Kruppe-1/+0
This does not actually improve build times, since it still depends on rustc_trans, but is better layering and fits the multi-backend future slightly better.
2017-05-15Remove rustc_llvm dependency from librustcRobin Kruppe-1/+0
Consequently, session creation can no longer initialize LLVM. The few places that use the compiler without going through rustc_driver/CompilerCalls thus need to be careful to manually initialize LLVM (via rustc_trans!) immediately after session creation. This means librustc is not rebuilt when LLVM changes.
2017-05-14Update to the oxidized rust-installerJosh Stone-3/+162
2017-05-14Remove rustc_llvm dependency from rustc_metadataRobin Kruppe-1/+18
Move the code for loading metadata from rlibs and dylibs from rustc_metadata into rustc_trans, and introduce a trait to avoid introducing a direct dependency on rustc_trans. This means rustc_metadata is no longer rebuilt when LLVM changes.
2017-05-13Pass static crt to llvm cmake configurationLiran Ringel-17/+17
2017-05-09Update save-analysis deps and RLS submoduleNick Cameron-7/+7
2017-05-07Auto merge of #41729 - ubsan:master, r=nrcbors-1/+1
Delete features which are easily removed, in libsyntax
2017-05-07fix the easy features in libsyntaxubsan-1/+1
2017-05-03convert save-analysis to use `ItemCtxt` and not `ast_ty_to_ty_cache`Niko Matsakis-0/+1
2017-05-03remove use of `ast_ty_to_ty_cache` from librustdocNiko Matsakis-0/+1
2017-04-29Auto merge of #41588 - cengizIO:master, r=nikomatsakisbors-0/+7
use diff crate for compile-fail test diagnostics #41474 Hello! This fixes #41474 We were using a custom implementation to dump the differences between expected and actual outputs of compile-fail tests. I removed this internal implementation and added `diff` crate as a new dependency to `compile-fail`. Again, huge thanks to @nikomatsakis for guiding.
2017-04-27travis: Parallelize tests on AndroidAlex Crichton-8/+8
Currently our slowest test suite on android, run-pass, takes over 5 times longer than the x86_64 component (~400 -> ~2200s). Typically QEMU emulation does indeed add overhead, but not 5x for this kind of workload. One of the slowest parts of the Android process is that *compilation* happens serially. Tests themselves need to run single-threaded on the emulator (due to how the test harness works) and this forces the compiles themselves to be single threaded. Now Travis gives us more than one core per machine, so it'd be much better if we could take advantage of them! The emulator itself is still fundamentally single-threaded, but we should see a nice speedup by sending binaries for it to run much more quickly. It turns out that we've already got all the tools to do this in-tree. The qemu-test-{server,client} that are in use for the ARM Linux testing are a perfect match for the Android emulator. This commit migrates the custom adb management code in compiletest/rustbuild to the same qemu-test-{server,client} implementation that ARM Linux uses. This allows us to lift the parallelism restriction on the compiletest test suites, namely run-pass. Consequently although we'll still basically run the tests themselves in single threaded mode we'll be able to compile all of them in parallel, keeping the pipeline much more full and using more cores for the work at hand. Additionally the architecture here should be a bit speedier as it should have less overhead than adb which is a whole new process on both the host and the emulator! Locally on an 8 core machine I've seen the run-pass test suite speed up from taking nearly an hour to only taking 6 minutes. I don't think we'll see quite a drastic speedup on Travis but I'm hoping this change can place the Android tests well below 2 hours instead of just above 2 hours. Because the client/server here are now repurposed for more than just QEMU, they've been renamed to `remote-test-{server,client}`. Note that this PR does not currently modify how debuginfo tests are executed on Android. While parallelizable it wouldn't be quite as easy, so that's left to another day. Thankfully that test suite is much smaller than the run-pass test suite. As a final fix I discovered that the ARM and Android test suites were actually running all library unit tests (e.g. stdtest, coretest, etc) twice. I've corrected that to only run tests once which should also give a nice boost in overall cycle time here.
2017-04-27Rollup merge of #41572 - frewsxcv:bump-mdbook, r=steveklabnikCorey Farwell-3/+3
Bump mdbook dep to pick up new 'create missing' toggle feature. This will avoid obscure Travis CI error messages: * https://github.com/rust-lang/rust/pull/40290#issuecomment-294137045 Original mdbook issue: * https://github.com/azerupi/mdBook/issues/253 mdbook PR: * https://github.com/azerupi/mdBook/pull/254
2017-04-27use diff crate for compile-fail test diagnostics #41474Cengiz Can-0/+7
2017-04-27Bump mdbook dep to pick up new 'create missing' toggle feature.Corey Farwell-3/+3
This will avoid obscure Travis CI error messages: * https://github.com/rust-lang/rust/pull/40290#issuecomment-294137045 Original mdbook issue: * https://github.com/azerupi/mdBook/issues/253 mdbook PR: * https://github.com/azerupi/mdBook/pull/254
2017-04-26Update num_cpus dependency to 1.x (1.4.0)Jessica Hamilton-3/+3
2017-04-19Rollup merge of #41374 - steveklabnik:update-mdbook, r=frewsxcvCorey Farwell-3/+3
update mdbook Ship some more improvements. r? @rust-lang/docs
2017-04-18Add top level sections to the Unstable Book.Corey Farwell-3/+0
Prior to this commit, the contents of the Unstable Book were assumed to be unstable features. This commit moves features into 'language features' or 'library features' subsections. It also moves the 'linker_flavor' compiler flag into a new 'Compiler Flags' subsection. Even though it was helpful, I removed the tidy check that cross-references the SUMMARY.md links with the Unstable Book directory contents just because it would be difficult to maintain. Relevant PR: https://github.com/rust-lang/rust/issues/41142.
2017-04-18update mdbooksteveklabnik-3/+3
2017-04-16rustc: expose monomorphic const_eval through on-demand.Eduard-Mihai Burtescu-2/+0
2017-04-16rustc_const_eval: move ConstEvalErr to the rustc crate.Eduard-Mihai Burtescu-2/+0
2017-03-31Sync all unstable features with Unstable Book; add tidy lint.Corey Farwell-0/+3
Add a tidy lint that checks for... * Unstable Book sections with no corresponding SUMMARY.md links * unstable features that don't have Unstable Book sections * Unstable Book sections that don't have corresponding unstable features
2017-03-28Fix id generationGuillaume Gomez-4/+5
2017-03-28Update to last pulldown versionGuillaume Gomez-35/+27
2017-03-28Update pulldown version after fix mergedGuillaume Gomez-1/+16
2017-03-28Replace hoedown with pull in rustdocGuillaume Gomez-0/+2
2017-03-23Remove internal liblogAlex Crichton-32/+21
This commit deletes the internal liblog in favor of the implementation that lives on crates.io. Similarly it's also setting a convention for adding crates to the compiler. The main restriction right now is that we want compiler implementation details to be unreachable from normal Rust code (e.g. requires a feature), and by default everything in the sysroot is reachable via `extern crate`. The proposal here is to require that crates pulled in have these lines in their `src/lib.rs`: #![cfg_attr(rustbuild, feature(staged_api, rustc_private))] #![cfg_attr(rustbuild, unstable(feature = "rustc_private", issue = "27812"))] This'll mean that by default they're not using these attributes but when compiled as part of the compiler they do a few things: * Mark themselves as entirely unstable via the `staged_api` feature and the `#![unstable]` attribute. * Allow usage of other unstable crates via `feature(rustc_private)` which is required if the crate relies on any other crates to compile (other than std).
2017-03-20travis: Don't set `RUST_LOG` globallyAlex Crichton-7/+7
I have a suspicion that this caused a large regression in cycle times by forcing the compiler to perform more checks on every `debug!` statement, so let's test this out by removing the `RUST_LOG` env var globally. This regression in cycle time was witnessed between [two] [builds] where the [PR] in question didn't do much suspicious. Judging by how the stage0 times *also* regressed though then this is my best guess. [two]: https://travis-ci.org/rust-lang/rust/builds/210149932 [builds]: https://travis-ci.org/rust-lang/rust/builds/210179995 [PR]: https://github.com/rust-lang/rust/pull/40446
2017-03-15Move to using 0.1 versions of crates, rather than GH linksNick Cameron-17/+17
Also adds a fixme and does cargo update
2017-03-15Handle feature=rustbuildNick Cameron-1/+1
Taken from https://github.com/rust-lang/rust/pull/40347/files And update rls-span to a version with the rustbuild boilerplate
2017-03-15Add rls-span to do some conversions into rls-data.Nick Cameron-0/+1
And fix some warnings and borrow errors
2017-03-15Use out-of-tree rustc serializeNick Cameron-12/+12
And remove a few data structures in favour of rls-data ones
2017-03-15save-analysis: depend on the rls-data crateNick Cameron-11/+42
2017-03-11Update mdbook to new versionsteveklabnik-40/+40
This brings back playpen integration for the books.
2017-03-10Don't put Cargo into the rustc workspaceAlex Crichton-666/+0
This causes problems when first cloning and bootstrapping the repository unfortunately, so let's ensure that Cargo sticks around in its own workspace. Because Cargo is a submodule it's not available by default on the inital clone of the rust-lang/rust repository. Normally it's the responsibility of the rustbuild to take care of this, but unfortunately to build rustbuild itself we need to resolve the workspace conflicts. To deal with this we'll just have to ensure that all submodules are in their own workspace, which sort of makes sense anyway as updates to dependencies as bugfixes to Cargo should go to rust-lang/cargo instead of rust-lang/rust. In any case this commit removes Cargo from the global workspace which should resolve the issues that we've been seeing. To actually perform this the `cargo` submodule has been moved to the top directory to ensure it's outside the scope of `src/Cargo.toml` as a workspace.
2017-03-04Automate timestamp creation and build skipping for native librariesVadim Petrochenkov-2/+2
Add comments
2017-03-04Support combination MSVC + NinjaVadim Petrochenkov-7/+7
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-09 15:24:39 +0000