about summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
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-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
2019-01-25Rebase to the llvm-project monorepoJosh Stone-20/+31
The new git submodule src/llvm-project is a monorepo replacing src/llvm and src/tools/{clang,lld,lldb}. This also serves as a rebase for these projects to the new 8.x branch from trunk. The src/llvm-emscripten fork is unchanged for now.
2019-01-25Correctly set filetime for copied LLVMMark Rousskov-4/+10
This also makes compiletest no longer always retest everything.
2019-01-25bootstrap: Don't rely on any default settings regarding incr. comp. in Cargo.Michael Woerister-0/+3
2019-01-24Remove quote_*! macros and associated APIsMark Simulacrum-24/+0
2019-01-21Auto merge of #57708 - nbigaouette:pr-53774-fix-missing-rust-gdbui-install, ↵bors-0/+2
r=Mark-Simulacrum Install missing 'rust-gdbui'' PR #53774 added `rust-gdbui` as wrapper to launch [gdbui](https://gdbgui.com/), similar to `rust-gdb`. Unfortunately I've never seen the script in my local installation (from rustup, using rust 1.31.1). @tromey on the PR [suggested it might be missing](https://github.com/rust-lang/rust/pull/53774#issuecomment-419704939) from the installation process. This PR simply adds a line for `rust-gdbui` too.
2019-01-20Auto merge of #57704 - lenoil98:patch-2, r=alexcrichtonbors-0/+3
Update bootstrap.py Add PowerPC64 support on FreeBSD
2019-01-20Auto merge of #57680 - cuviper:codegen-rebuild, r=Mark-Simulacrumbors-0/+12
[rustbuild] Rebuild std after changes to codegen backends Use `clear_if_dirty` on std for backend changes, just as we do for changes to rustc itself, so new codegen is correctly applied to all later compiler stages. Fixes #48298.
2019-01-19Auto merge of #57370 - petrhosek:llvm-flags, r=alexcrichtonbors-1/+28
Support passing cflags/cxxflags/ldflags to LLVM build This may be needed with some host compilers.
2019-01-17Fix typo: 'rust-gdbgui' instead of 'rust-gdbui'Nicolas Bigaouette-1/+1
2019-01-17Install missing 'rust-gdbui''Nicolas Bigaouette-0/+2
See https://github.com/rust-lang/rust/pull/53774#issuecomment-419704939
2019-01-17Update bootstrap.pylenoil98-0/+3
Add PowerPC64 support on FreeBSD
2019-01-17compiletest: Simplify handling of Clang-based tests.Michael Woerister-16/+9
2019-01-17Support clang-based run-make tests in rustbuild.Michael Woerister-5/+30
2019-01-16[rustbuild] Rebuild std after changes to codegen backendsJosh Stone-0/+12
Use `clear_if_dirty` on std for backend changes, just as we do for changes to rustc itself, so new codegen is correctly applied to all later compiler stages. Fixes #48298.
2019-01-13Support passing cflags/cxxflags/ldflags to LLVM buildPetr Hosek-1/+28
This may be needed with some host compilers.
2019-01-13Adding Build automation for x86_64-fortanix-unknown-sgxVardhan Thigle-20/+33
2019-01-12Rollup merge of #57368 - petrhosek:cmake-compiler-launcher, r=alexcrichtonMazdak Farrokhzad-8/+6
Use CMAKE_{C,CXX}_COMPILER_LAUNCHER for ccache CMake 3.4 and newer which is the required minimum version for LLVM supports CMAKE_{C,CXX}_COMPILER_LAUNCHER for settting the compiler launcher such as ccache which doesn't require shifting arguments.
2019-01-10Integrate miri into build-manifestAlex Crichton-1/+1
This fixes a mistake where miri was accidentally left out of the build-manifest parsing, meaning that today's nightly generated a manifest with invalid urls!
2019-01-09Auto merge of #57086 - oli-obk:miri_dist, r=kennytmbors-0/+152
Prepare everything for distributing miri via rustup The next step is to tell rustup about `cargo-miri` in https://github.com/rust-lang/rustup.rs/blob/31935e5f633a5acd3a203d23b61d1556c64a821c/src/rustup/lib.rs#L28 and https://github.com/rust-lang/rustup.rs/blob/1ccd706d1d572c777c5134bd7db7aa1a8df7f278/src/rustup-win-installer/src/lib.rs#L29
2019-01-08fixupOliver Scherer-2/+46
2019-01-08Prepare everything for distributing miri via rustupOliver Scherer-0/+108
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 18:03:16 +0000