about summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
2019-03-09Rollup merge of #58676 - euclio:bootstrap-python, r=alexcrichtonMazdak Farrokhzad-8/+10
look for python2 symlinks before bootstrap python Before this commit, if you're running x.py directly on a system where `python` is symlinked to Python 3, then the `python` config option will default to a Python 3 interpreter. This causes debuginfo tests to fail with an opaque error message, since they have a hard requirement on Python 2. This commit modifies the Python probe behavior to look for python2.7 and python2 *before* using the interpreter used to execute `x.py`.
2019-03-08Rollup merge of #58269 - taeguk:add-some-sources-to-rust-src-distribution, ↵Pietro Albini-0/+2
r=Mark-Simulacrum Add librustc and libsyntax to rust-src distribution. Fixes #58268.
2019-03-08Rollup merge of #58080 - MikaelUrankar:freebsd_arm, r=sanxiynPietro Albini-0/+4
Add FreeBSD armv6 and armv7 targets
2019-03-06Make Cargo a rustc tool againJohn Kåre Alsaker-2/+2
2019-03-05Add librustc, libsyntax to rust-src distribution.Taeguk Kwon-0/+2
2019-03-05Bootstrap changesJohn Kåre Alsaker-36/+96
2019-03-02Bootstrap compiler update for 1.35 releaseMark Rousskov-1/+1
2019-03-01look for python2 symlinks before bootstrap pythonAndy Russell-1/+1
Before this commit, if you're running x.py directly on a system where `python` is symlinked to Python 3, then the `python` config option will default to a Python 3 interpreter. This causes debuginfo tests to fail with an opaque error message, since they have a hard requirement on Python 2. This commit modifies the Python probe behavior to look for python2.7 and python2 *before* using the interpreter used to execute `x.py`.
2019-03-01fix an issue with path probing on WindowsAndy Russell-7/+9
The old logic would incorrectly look for "python2.exe" when searching for "python2.7.exe".
2019-03-01Auto merge of #58800 - ehuss:update-books, r=Centrilbors-1/+1
Update edition-guide 15 commits in 419edb885ec1a98c0747b3907003d79e3e6b93a9..5f3cc2a5618700efcde3bc00799744f21fa9ad2e 2018-12-04 16:43:38 -0500 to 2019-02-27 20:11:50 -0800 - Migrate to mdbook 0.2. (rust-lang-nursery/edition-guide#152) - Remove automatic deployment. (rust-lang-nursery/edition-guide#151) - Fix issue with rust's linkchecker and mdbook. (rust-lang-nursery/edition-guide#147) - Fix test now that overflowing_literals is rejected in all editions. (rust-lang-nursery/edition-guide#148) - overflowing_literals is deny on all editions (rust-lang-nursery/edition-guide#146) - Update for uniform_path stabilization. (rust-lang-nursery/edition-guide#141) - Add example to rustup to show overriding to specific version (rust-lang-nursery/edition-guide#144) - Update for anonymous-lifetime stabilization. (rust-lang-nursery/edition-guide#142) - Add minimum Rust version for Kleene operator (rust-lang-nursery/edition-guide#137) - Add 2018-specific changes. (rust-lang-nursery/edition-guide#130) - aborting-on-panic.md: Typo in example config (rust-lang-nursery/edition-guide#125) - Clarify uniform paths are not yet in Rust 2018 (rust-lang-nursery/edition-guide#124) - update several version numbers - Fixes outdated link (rust-lang-nursery/edition-guide#131) - Fixed typo in transitioning page. (rust-lang-nursery/edition-guide#127)
2019-03-01Auto merge of #58408 - alexcrichton:update-llvm, r=michaelwoeristerbors-0/+7
rustc: Update LLVM, remove dead wasm code This commit updates the LLVM branch to the rebased version of the upstream release/8.x branch. This includes a wasm patch which means that the `rewrite_imports` pass in rustc is no longer needed (yay!) and we can instead rely on `wasm-import-module`, an attribute we're already emitting, to take care of all the work.
2019-02-28Introduce rustc_interface and move some methods thereJohn Kåre Alsaker-0/+2
2019-02-27Update edition-guideEric Huss-1/+1
2019-02-27Whitelist containers that allow older toolchainsAlex Crichton-0/+7
We'll use this as a temporary measure to get an LLVM update landed, but we'll have to go through and update images later to make sure they've got the right toolchains.
2019-02-27Rollup merge of #58680 - varkor:xpy-help-index-error, r=alexcrichtonMazdak Farrokhzad-1/+1
Fix an indexing error when using `x.py help` Fixes https://github.com/rust-lang/rust/issues/58640.
2019-02-25bootstrap: deny(rust_2018_idioms)Taiki Endo-315/+352
2019-02-25Rollup merge of #58704 - taiki-e:extern-crate, r=CentrilMazdak Farrokhzad-20/+0
Remove some unnecessary 'extern crate' cc #58099 r? @Centril
2019-02-25Remove some unnecessary 'extern crate'Taiki Endo-20/+0
2019-02-24Use ? in some macrosTaiki Endo-1/+1
2019-02-23Fix an indexing error when using `x.py help`varkor-1/+1
2019-02-17Rollup merge of #57929 - GuillaumeGomez:rustodc-remove-old-style-files, ↵kennytm-6/+23
r=ollie27 Rustdoc remove old style files Reopening of #56577 (which I can't seem to reopen...). I made the flag unstable so with this change, what was blocking the PR is now gone I assume.
2019-02-13Add FreeBSD armv6 and armv7 targetsMikaelUrankar-0/+4
2019-02-13Auto merge of #58238 - Mark-Simulacrum:doctest-fix, r=alexcrichtonbors-24/+23
Fixes rustdoc in stage 0, stage 1 When a request for rustdoc is passed for stage 0, x.py build --stage 0 src/tools/rustdoc or ensure(tool::Rustdoc { .. }) with top_stage = 0, we return the rustdoc for that compiler (i.e., the beta rustdoc). This fixes stage 0 of https://github.com/rust-lang/rust/issues/52186 as well as being part of general workflow improvements (making stage 0 testing for std work) for rustbuild. The stage 1 fix (second commit) completely resolves the problem, so this fixes https://github.com/rust-lang/rust/issues/52186.
2019-02-11This fixes doctests in stage 1Mark Rousskov-24/+17
The RUSTDOC_LIBDIR should be rustc_libdir, not sysroot_libdir; rustdoc is like the compiler and should link against rustc's libdir. Some people currently (i.e., in general, may not be on master) have doc tests working, but no attempt to determine why has been attempted.
2019-02-11Never build rustdoc in stage 0Mark Rousskov-0/+6
When a request for rustdoc is passed for stage 0, x.py build --stage 0 src/tools/rustdoc or ensure(tool::Rustdoc { .. }) with top_stage = 0, we return the rustdoc for that compiler (i.e., the beta rustdoc).
2019-02-10rustc: doc commentsAlexander Regueiro-38/+38
2019-02-09Add EmbeddedBook to test list in bootstrapMark Rousskov-0/+1
2019-02-08Deny warnings in std stage 0varkor-2/+1
2019-02-06Add embedded book to test such that checktools worksMark Rousskov-0/+1
2019-02-04Add embedded bookJames Munns-4/+2
2019-02-01Auto merge of #57937 - denzp:nvptx, r=nagisabors-2/+3
NVPTX target specification This change adds a built-in `nvptx64-nvidia-cuda` GPGPU no-std target specification and a basic PTX assembly smoke tests. The approach is taken here and the target spec is based on `ptx-linker`, a project started about 1.5 years ago. Key feature: bitcode object files being linked with LTO into the final module on the linker's side. Prior to this change, the linker used a `ld` linker-flavor, but I think, having the special CLI convention is a more reliable way. Questions about further progress on reliable CUDA workflow with Rust: 1. Is it possible to create a test suite `codegen-asm` to verify end-to-end integration with LLVM backend? 1. How would it be better to organise no-std `compile-fail` tests: add `#![no_std]` where possible and mark others as `ignore-nvptx` directive, or alternatively, introduce `compile-fail-no-std` test suite? 1. Can we have the `ptx-linker` eventually be integrated as `rls` or `clippy`? Hopefully, this should allow to statically link against LLVM used in Rust and get rid of the [current hacky solution](https://github.com/denzp/rustc-llvm-proxy). 1. Am I missing some methods from `rustc_codegen_ssa::back::linker::Linker` that can be useful for bitcode-only linking? Currently, there are no major public CUDA projects written in Rust I'm aware of, but I'm expecting to have a built-in target will create a solid foundation for further experiments and awesome crates. Related to #38789 Fixes #38787 Fixes #38786
2019-01-31Add missing generation for test and proc_macro, remove old macro redirectionGuillaume Gomez-8/+23
2019-01-31Auto merge of #57514 - michaelwoerister:xlto-tests, r=alexcrichtonbors-17/+55
compiletest: Support opt-in Clang-based run-make tests and use them for testing xLTO. Some cross-language run-make tests need a Clang compiler that matches the LLVM version of `rustc`. Since such a compiler usually isn't available these tests (marked with the `needs-matching-clang` directive) are ignored by default. For some CI jobs we do need these tests to run unconditionally though. In order to support this a `--force-clang-based-tests` flag is added to compiletest. If this flag is specified, `compiletest` will fail if it can't detect an appropriate version of Clang. @rust-lang/infra The PR doesn't yet enable the tests yet. Do you have any recommendation for which jobs to enable them? cc #57438 r? @alexcrichton
2019-01-31Rollup merge of #57920 - euclio:source-date-epoch, r=Mark-SimulacrumMazdak Farrokhzad-2/+14
use `SOURCE_DATE_EPOCH` for man page time if set Fixes #57776.
2019-01-30bootstrap: Expose LLVM_USE_LINKER cmake option to config.toml.Michael Woerister-0/+7
2019-01-30bootstrap: Make LLD available to run-make tests.Michael Woerister-14/+27
2019-01-30No consumers of MdBook2 yetJames Munns-0/+4
2019-01-30Only the compatibility items from the embedded book PRJames Munns-8/+33
PR: https://github.com/rust-lang/rust/pull/56291
2019-01-29Auto merge of #57953 - mati865:cc-fix, r=alexcrichtonbors-9/+4
Do not set CC, CFLAGS, CXX, CXXFLAGS, AR, RANLIB in bootstrap, it breaks cross compilation Fixes https://github.com/rust-lang/rust/issues/57812 I tested it in AArch64 Ubuntu container with several days old tree to have all the tools buildable. I did **not** test native builds (amd64 -> amd64), leaving it to CI. r? @alexcrichton
2019-01-28bootstrap: set toolchain variables on per target basisMateusz Mikuła-9/+4
Using CC, CFLAGS, CXX, CXXFLAGS, AR and RANLIB breaks cross compilation because host is built first and has correct values. The same values are incorrect for the target however.
2019-01-28Fix CIJohn Kåre Alsaker-1/+1
2019-01-28Use multiple threads by default. Limits tests to one thread. Do some renaming.John Kåre Alsaker-7/+7
2019-01-27Auto merge of #57765 - Mark-Simulacrum:bootstrap-bump, r=alexcrichtonbors-5/+17
Bump bootstrap compiler to 1.33 beta r? @alexcrichton or @pietroalbini cc @rust-lang/release
2019-01-27Create `nvptx64-nvidia-cuda` target specificationDenys Zariaiev-2/+3
2019-01-27Add generate-old-style-files option to rustdocGuillaume Gomez-1/+3
2019-01-27Auto merge of #57871 - Mark-Simulacrum:fix-compiletest-stamp, r=oli-obkbors-4/+10
Correctly set filetime for copied LLVM This also makes compiletest no longer always retest everything. Fixes #57864
2019-01-26use `SOURCE_DATE_EPOCH` for man page time if setAndy Russell-2/+14
2019-01-26Workaround presence of LLVM library in stage0/libMark Rousskov-2/+14
This commit works around the newly-introduced LLVM shared library. This is needed such that llvm-config run from librustc_llvm's build script can correctly locate it's own LLVM, not the one in stage0/lib. The LLVM build system uses the DT_RUNPATH/RUNPATH header within the llvm-config binary, which we want to use, but because Cargo always adds the host compiler's "libdir" (stage0/lib in our case) to the dynamic linker's search path, we weren't properly finding the freshly-built LLVM in llvm/lib. By restoring the environment variable setting the search path to what bootstrap sees, the problem is resolved and librustc_llvm correctly links and finds the appropriate LLVM. Several run-make-fulldeps tests are also updated with similar handling.
2019-01-26Bump bootstrap compiler to 1.33 betaMark Rousskov-3/+3
2019-01-25Set LLDB_NO_DEBUGSERVER=ONJosh Stone-0/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 09:03:35 +0000